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=12598>. 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=12598 Apache hanging in Keepalive State ------- Additional Comments From [EMAIL PROTECTED] 2004-02-11 23:31 ------- found this same problem as well, able to reproduce always. (linux) 1.3.29, mod_ssl-2.8.16-1.3.29, php 4.3.4 I didn't try the Browsermatch directives here but I don't believe it will help as there is no further traffic at all between the "stuck" ip and the server once in this state, other than tcp keepalives which is how the connection can stay established forever or else the tcp keepalive timeout in the kernel would close it. (Give me a reason to try disabling keepalives or something though and I will but I'm working off a production system and can't play much now that it's working). SIGALRM to the child doesn't do anything, SIGUSR2 kills it, so the work around I've had to do is change this signal to alrm_handler in child_main() in http_main.c and not define OPTIMIZE_TIMEOUTS. So, I don't really like this because it means every time a child reaches KeepAliveTimeout seconds, it dies and apache is pretty busy always spawning new children. (And the error log has a lot of messages [notice] child pid 28392 exit signal Alarm clock (14) :) Also, yes mod_ssl is loaded but the hung processes I've seen were all serving from http vhosts. Is it mod_ssl or libphp4 intercepting the SIGALRM? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
