httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10318] New: - Apache 2.0.36 - 2.0.39 become unresponsive
Date Fri, 28 Jun 2002 11:55:00 GMT
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=10318>.
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=10318

Apache 2.0.36 - 2.0.39 become unresponsive

           Summary: Apache 2.0.36 - 2.0.39 become unresponsive
           Product: Apache httpd-2.0
           Version: 2.0.39
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: Major
          Priority: Other
         Component: prefork
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: info@orangexl.com


After about 48 to 72 hours (in my case), the httpd-error log start to write 
messages like "long lost child came home". Shortly after that, messages in the 
form of "Warn (61) Connection refused: Connect to listener" start to appear, 
soon 1 every second. Apache refuses any connection (time out) and the server 
becomes very unresponesive. A restart is the only solution. Problem occurred in 
2.0.36 and 2.0.39. Never had it with 2.0.35.

As far as I can see (newbie), I would say it's a problem in prefork.c. Also, it 
could be related with bug 10302

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message