SUMMARY: error-logging stopped

From: T. Horsnell <tsh_at_mrc-lmb.cam.ac.uk>
Date: Tue, 31 Jan 2006 17:30:23 +0000 (GMT)

Thanks to all who suggested things like:

kill -USR1 `cat /var/run/binlogd.pid`
kill -HUP `cat /var/run/binlogd.pid`
/sbin/init.d/binlog stop
/sbin/init.d/binlog start

None of these worked.
kill -USR1 didnt save the old errorlog and start a new one.
/sbin/init.d/binlog stop didnt stop the binlogd (I did
check that the actual pid was the same as the contents
of binlogd.pid)

I had to kill -9 `cat /var/run/binlogd.pid`
to stop the binlogd, and then use /sbin/init.d/binlog start
to restart it. Then, kill -USR1 `cat /var/run/binlogd.pid`
cycled the binary.errorlog as advertised.

Now back to that tapedrive error...

Cheers,
Terry.
Received on Tue Jan 31 2006 - 17:31:20 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:45 NZDT