DO NOT REPLY [Bug 14647] - apachectl doesn't sufficiently check for previously running instances

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=14647>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=14647

apachectl doesn't sufficiently check for previously running instances

andrew@scoop.co.nz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew@scoop.co.nz
           Priority|Other                       |Medium



------- Additional Comments From andrew@scoop.co.nz  2004-05-20 05:36 -------

I just got burned by this one.  I'm surprised it hasn't generated more attention.

In my case the apache instance (one of several) had been started at system
startup with a low numbered PID.  The server had crashed, leaving the pid file
in place.  It's fairly unsurprising that on the subsequent startup another
server process was using the same low numbered PID.

Given several apache instances, it's not always going to be possible to rely on
the PID in the PIDFILE identifying a running httpd process.  Checking the
creation time of the PID file against the creation time of the identified
process might be a good approach.

Wiping out PID files early in a boot sequence is probably a helpful workaround
and will prevent most problems.  This is necessarily outside the scope of the
apache source code.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org