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 2003/02/28 23:51:17 UTC
DO NOT REPLY [Bug 17548] -
Hanging httpd processes... trace below
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=17548>.
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=17548
Hanging httpd processes... trace below
------- Additional Comments From mike@epicworks.com 2003-02-28 22:51 -------
Basically, at what appears to be random intervals, it gets to this point, and
the process just stops at that last SELECT noted below. So the process does
nothing useful from then on. Eventually it increases the clients until it
reaches MaxClients and then everyone just waits permenantly. and no requests
get served.
sending a graceful restart just adds the following...
= ? ERESTARTNOHAND (To be restarted)
--- SIGUSR1 (User defined signal 1) @ 0 (0) ---
select(11, NULL, [10], [10], NULL
and we appear to be back where we started.
Using GLIBC2.3.1 if it affects anything.
Any thoughts? This appears ot be just on this one server.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org