httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22631] - Apache2 crashs and can not be closed from task manager until reboot
Date Fri, 24 Oct 2003 04:52:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22631>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22631

Apache2 crashs and can not be closed from task manager until reboot

robert@profundis.se changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |robert@profundis.se
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From robert@profundis.se  2003-10-24 04:52 -------
> now question: how PHP can can cause apache die so hard, that even OS can not
> clean up the mess?

Apache on Windows runs in two processes; the main "listener" and the "worker".
The former takes care of housekeeping etc, while the latter does the actual
serving. When crashing, it is almost always the latter, and the main process can
spawn a new one. I don't know what caused your Apache to hang so long before
spawning the new worker process, but I have a feeling it might be related to
rotatelogs.

I change the report's status to INVALID, as the main issue (crashing) was PHP
related, although the hanging is yet unresolved. Feel free to re-open it.

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


Mime
View raw message