[clue-admin] Logrotate is b0rked

[Jed S. Baer]

On Sun, 27 Mar 2005 12:52:15 -0700
David Anselmi wrote:

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

Nope. 1 message, occurring twice in the avilable logs:

logrotate: ALERT exited abnormally with [1]

To make matters slightly worse, logrotate decided, after I fixed up the
logs yesterday, that lastnight would be a good time to try again, so we
now have all the active logs with a "rotated" file name. Not that that
really hurts anything in the short term.

> 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.)

Yeah, that was the first thing I looked at.

I guess I'll throw some diagnostics into the logrotate job. Something
along the lines of

exec >> /root/logrotate.log 2>&1
set -x

jed
-- 
http://s88369986.onlinehome.us/freedomsight/
Key fingerprint = B027 FEFB 4281 CC72 67D1  4237 F2D0 D356 077A A30E
... it is poor civic hygiene to install technologies that could someday
facilitate a police state. -- Bruce Schneier