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=21322>. 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=21322 main worker process locks up and no longer accepts requests ------- Additional Comments From [EMAIL PROTECTED] 2003-07-08 02:29 ------- I am pretty sure that is from the main apache process which runs as root, but the backtrace is for the main process. I just did a gcore of a an apache 2 main process on a server running normally and the backtrace for the main process and its three threads look identical to the gcore generated for the root process when apache 2 was not accepting requests. After comparing the two I realized that my diagnosis of the problem I originally posted is flawed. Thanks for pointing out my bad assumptions. :-) Here is what I am seeing. A child process fails with a coredump. From that time on apache 2 is still bound to port 80 but does not respond to HTTP requests. Our system monitoring software does not detect that Apache 2 has failed. Usually a stop/start of apache 2 will solve the problem. This doesn't happen everytime a child process dies. There are no error messages other than that the child process died. LogLevel is set to WARN. Can a hung child cause this behaviour? The next time this happens I will make sure gcore is used to generate a core file for all the apache processes. Thanks, glenn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
