You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/05/28 17:08:19 UTC

DO NOT REPLY [Bug 29277] - Apache gets locked

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=29277>.
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=29277

Apache gets locked





------- Additional Comments From trawick@apache.org  2004-05-28 15:08 -------
Best doc for a web server hang condition is to run pstack against each web
server process and post the results.

There are two known issues which you may be suffering from:

1) ssl-related child process crash introduced in 2.0.49

See PR27945.  Here is the fix for that problem:

http://cvs.apache.org/viewcvs.cgi/httpd-2.0/modules/ssl/ssl_engine_io.c?r1=1.121&r2=1.122

2) hang after crash when using pthread accept mutex (the default on Solaris)

(this is not at all obvious from your truss, but pstack of all children when in
this hung state should give more definitive info)

Very possibly the child process crash (segmentation fault) resulted in screwing
up the accept mutex, which in turn hung the server.

Try switching to non-default accept mutex type, by adding this to httpd.conf:

AcceptMutex fcntl

This has nothing to do with the child process crash, but it should resolve web
server hangs that occur after a crash due to loss of accept mutex.

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