DO NOT REPLY [Bug 10266] - apache hangs after some hours of running

From: <bugzilla(at)apache.org>
Date: Tue Jul 23 2002 - 22:27:26 EDT

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

apache hangs after some hours of running

• Additional Comments From dcook@cookware.com 2002-07-24 02:27 ------- I'll mention this, in case it is significant...

We have a program that remotely monitors to see if our servers are up. The program also monitors apache. It senses the apache hanging, but no matter what I do to the code, setting a SIGNAL and an ALARM in all of my socket code (open, read/write and close all have alarms around them) it MOSTLY will not catch it. In other words, the call to read from the socket reads and an ALARM does not break it out of the read.

Additionally, in support of this, I also noted that a HUP to the parent process (apache) does not free it up. Additionally, if I TELNET to port 80 of the hung process IP address, I get a connection from apache, but issuing a "GET /" causes a hang (as I previously reported)... HOWEVER, trying to break that hang with a CONTROL-C or other signal, OTHER than a kill, also refuses to free the hang.

So, it seems to me that other than a kill signal, when these are hanging other signals are also refused (e.g., alarm, control-c (int)).

---

To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org Received on Wed Jul 24 02:27:01 2002