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 42473] New: - Apache2 problem with MaxClient and/or TimeOut
Date Mon, 21 May 2007 16:33:49 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42473>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42473

           Summary: Apache2 problem with MaxClient and/or TimeOut
           Product: Apache httpd-2
           Version: 2.0.54
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: prefork
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: borja.pacheco@juntadeandalucia.es


Dear all,

we have a webmail platform based on Reverse Proxies + Apache + Squirrelmail. 

Lately we updated Apache's from 1.3.x to 2.0.54 (using standard Sarge Debian
packages), since this update, we are watching that Apache reaches MaxClients
often (once or twice daily), and the only one way to restore the service is to
restart the daemon.

Luckly, we have been able to test a "hanged-up" server, and we made several
test/meassures:
1. We noticed that MaxClients works, because it's configured to manage X clients
and there're X processes runing into de OS.
2. We watched that we had X established connections too.
At this point everything looks fine, but there are a few strange things...
3. The connection among reverse proxy and apaches didn't carry data, just ACKs.
Why isn't TimeOut rejecting this connections?
4. In order to verify who's working bad Apache or Proxies (Although the haven't
been cahnged during the update), we inserted a rule into the firewall rejecting
any input packet to the webserver.
Result: connections became closed, but only after 45 minutes (and our TimeOut is
configured in 120 seconds...!)
5. Once connections closed, we hoped that processes should be removed, and the
server will start to accept new incoming requests. Not as expected, the server
is still "hanged-up".

Data:
MDM: Prefork

ii  apache-common  1.3.33-6sarge3 support files for all Apache webservers
ii  apache2        2.0.54-5sarge1 next generation, scalable, extendable web se
ii  apache2-common 2.0.54-5sarge1 next generation, scalable, extendable web se
ii  apache2-mpm-pr 2.0.54-5sarge1 traditional model for Apache2
ii  apache2-utils  2.0.54-5sarge1 utility programs for webservers
ii  libapache2-mod 4.3.10-19      server-side, HTML-embedded scripting languag

LockFile /var/lock/apache2/accept.lock
PidFile /var/run/apache2.pid
Timeout 120
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimeout 15
ServerTokens Prod

<IfModule prefork.c>
StartServers        10
MinSpareServers     10
MaxSpareServers     15
MaxClients          25
MaxRequestsPerChild 1000
</IfModule>

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message