[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Logrotate or Apache not using /var/log/httpd/errors after cron.daily
- Subject: [cobalt-users] Logrotate or Apache not using /var/log/httpd/errors after cron.daily
- From: Paul Warner <pwarner@xxxxxxxxxxxxxxxxxx>
- Date: Wed Jan 29 10:35:01 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
I'm not sure who's not behaving, but SOME days apache will not log to the
/var/log/httpd/errors file. Using /etc/rc.d/init.d/httpd reload or restart
will cause it to begin again. There have been no issues with it failing to
log into access or other files, just ~50% of the time it messes up on the
error log.
Permissions on all files are identical, as are owner/group. Logrotate
settings are (in order they appear):
/var/log/httpd/access {
prerotate
/usr/local/sbin/split_logs web < /var/log/httpd/access
endscript
missingok
postrotate
/usr/bin/killall -HUP httpd 2> /dev/null || true
endscript
daily
}
/var/log/httpd/error {
missingok
postrotate
/usr/bin/killall -HUP httpd 2> /dev/null || true
endscript
daily
}
I can also execute the '/usr/bin/killall -HUP httpd 2> /dev/null || true'
command from a shell as root and get it to restart. There are no error
reports from logrotate, httpd, or cron. Normally, as least the 'resuming
normal operations' message starts the new log...
-- Paul