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

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 trawick@apache.org 2002-11-24 19:50 ------- Here is some info that would be helpful. I realize that you have sent some of this to particular individuals in the past, but I don't see it in the PR.

At the time of the hang:

  how many child processes and what are they doing? (run pstack against   each one to see what is going on; presumably most of the children will   have the same backtrace, so no sense sending in duplicate backtraces)

  what is the parent doing? run truss against it for a while (15 seconds)   if it doesn't appear to be doing anything, run pstack against it to   get a backtrace

  is it possible that all available children are handling connections?   look at netstat output for ports served by Apache to see if there are   enough hung connections to represent each available child

wild and crazy idea:

  try a different accept mutex mechanism (e.g., "AcceptMutex fcntl" in   httpd.conf)

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek