On Wed, Apr 16, 2003 at 11:56:45AM -0600, David Wilk wrote: Hi, > Hello all, > > I think I have found that an /etc/init.d/apache-ssl restart is the only > way to properly restart apache-ssl after a logrotation. However, I've > had apache-ssl die two days in a row, and the culprit appears to be some > process that is sending apache-ssl a SIGUSR1 (what apache-ssl reload or > httpsdctl graceful issues). > > Here's the log: > > [Mon Apr 14 03:00:18 2003] [notice] SIGUSR1 received. Doing graceful > restart > [Mon Apr 14 03:00:18 2003] /usr/lib/apache-ssl/gcache started > [Mon Apr 14 03:00:19 2003] [error] (2)No such file or directory: > mod_mime_magic: ca > n't read magic file /etc/apache-ssl/share/magic > [Mon Apr 14 03:00:19 2003] [notice] Apache/1.3.26 Ben-SSL/1.48 (Unix) > Debian GNU/Li > nux PHP/4.1.2 mod_perl/1.26 configured -- resuming normal operations > [Mon Apr 14 03:00:19 2003] [notice] suEXEC mechanism enabled (wrapper: > /usr/lib/apa > che-ssl/suexec) > [Mon Apr 14 03:00:19 2003] [notice] Accept mutex: sysvsem (Default: > sysvsem) > > the problem is I don't know what could possibly be issueing this SIGUSR1 > signal to apache-ssl every morning at the exact same time that cron runs > /etc/cron.daily. I've checked all my cron jobs and can't seem to find > the culprit. > > if anyone has any ideas, I'd be grateful.
It's logrotate that is invoked by cron - on RedHats it's configuration is in /etc/logrotate.d/apache for apache -- Best regards, -Vlad
