[clue-admin] Logrotate is b0rked

David Anselmi anselmi at anselmi.us
Sun Mar 27 12:52:15 MST 2005


Jed S. Baer wrote:
> I'm looking at the CLUE server logs, and noticing, again, that logrotate
> isn't working properly.
[...]
> Note that the "current" logfiles by name are all 0 bytes, whereas the
> active logs are the .1 versions. This implies that logrotate is renaming
> the files, but failing to execute its postrotate commands.

The only time I've seen this is when Debian messed up the postrotate 
command for exim (more than once, sadly).  But Debian doesn't use 
logrotate for syslog files so I can't say much more than that.

Are you seeing the syslogd restart entries in the logs when the 
logrotate cron runs?

The only explanation I can come up with is that syslogd's PID is 
different than /var/run/syslogd.pid.  (I can't check, the .pid file is 
readable only by root, even though ps happily tells me what syslogd's 
PID is.)

Dave



More information about the clue-admin mailing list