RE: Apache SIGHUP's - WHY?

["Mike Vanecek" <rh_lists mm-vanecek com>]

---------- Original Message -----------
From: "Burke, Thomas G." <tgburke northropgrumman com>
To: "'redhat-list redhat com'" <redhat-list redhat com>
Sent: Thu, 23 Jan 2003 09:00:59 -0800
Subject: RE: Apache SIGHUP's - WHY?

> -----BEGIN PGP SIGNED MESSAGE-----
> Kewl, thanks.  I'd never noticed it before, but that makes perfect
> sense.
> 
> - -Tom
> 
> - -----Original Message-----
> From: Gary Stainburn [mailto:gary stainburn ringways co uk]
> Sent: Thursday, January 23, 2003 10:54 AM
> To: Burke, Thomas G.; redhat-list redhat com
> Subject: Re: Apache SIGHUP's - WHY?
> 
> On Thursday 23 Jan 2003 3:25 pm, Burke, Thomas G. wrote:
> > Hey gang,
> >
> > 	I've been noticing this in my logs off & on, & it seems odd to me.
> > Can anyone explain?
> >
> > 	-Tom
> >
> > [Wed Jan 22 04:02:03 2003] [notice] SIGHUP received.  Attempting to
> > restart
> > [Wed Jan 22 04:02:03 2003] [notice] Apache/1.3.27 (Unix)
> > (Red-Hat/Linux) configured -- resuming normal operations
> 	> [Wed Jan 22 04:02:03 2003] [notice] Accept mutex: sysvsem
> (Default:
> > sysvsem)
> 
> Hi Tom,
> 
> You'll probably find that you've got a logrotate job in your crontab.
>  This is 
> a nice tidy way of keeping your log files tidy.
> 
> What this does is scrolls down your logfiles, e.g. .3 becomes .4, .2
> to .3, .1 
> to .2 and your current logfile becomes .1.  It then creates a new
> empty log.
> 
> However, Apache has an open file handle that is still pointing to the
> old 
> logfile.  Sending a HUP to Apache tells it to do a gracefull restart
> which 
> amongst other things makes it close/reopen the log file.
> 
> HTH
> 
> Gary
------- End of Original Message -------
Can anyone tell me why the Apache child processes have a problem stopping when
the log is rotated?  Can something be done to make the process cleaner?


[Thu Jan 23 03:13:01 2003] [warn] child process 8793 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:01 2003] [warn] child process 8794 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:01 2003] [warn] child process 8795 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:01 2003] [warn] child process 8796 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:01 2003] [warn] child process 8797 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:01 2003] [warn] child process 8798 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:01 2003] [warn] child process 8799 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:01 2003] [warn] child process 8800 did not exit, sending
another SIGHUP
[Thu Jan 23 03:13:02 2003] [notice] SIGHUP received.  Attempting to restart
[Thu Jan 23 03:13:03 2003] [notice] Apache/1.3.26 (Unix)  (Red-Hat/Linux)
mod_ssl/2.8.9 OpenSSL/0.9.6 PHP/4.1.1 mod_perl/1.24_01 FrontPage/5.0.2.2510
configured -- resuming normal operations
[Thu Jan 23 03:13:03 2003] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Thu Jan 23 03:13:03 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)