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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | Version|2.0.43 |2.0.44 ------- Additional Comments From [EMAIL PROTECTED] 2003-03-31 23:58 ------- Under 2.0.44 we are still experiencing this problem. We have noted that of the three servers running it occus on all three... and it occurs with more frequency on the busier servers. We currently have special software running to detect the hung process and REHUP (kill - USR1) it. REHUPPING apache fixes it in 99.9% of the cases (after 3 rehups fail in sequence our software automatically kills and restarts apache). We have also noted that in most cases apache itself will catch the hung child eventually (many minutes - which is why we wrote the software to detect it in 15 seconds or less). As a new clue to help you trace this down we have notice the following error messages in the error logs AFTER a HUP (kill -USR1) is done: [Mon Mar 31 18:49:28 2003] [notice] Graceful restart requested, doing restart [Mon Mar 31 18:49:33 2003] [notice] Apache/2.0.44 (Unix) mod_ssl/2.0.44 OpenSSL/ 0.9.6g configured -- resuming normal operations [Mon Mar 31 18:49:33 2003] [warn] long lost child came home! (pid 11039) [Mon Mar 31 18:49:33 2003] [warn] long lost child came home! (pid 11040) (that was in the log immediatly following our REHUP). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
