Apache 'MaxClients exceeded' error.
- Article Type: General
- Product: Aleph
- Product Version: 16.02
Since a month or two our Webopac is suffering from an overload of HTTPD daemons which is resulting in a Apache 'MaxClients exceeded' error.
We're closely monitoring\analyzing every case but we're not able to get the source of the problem.
-It seems that number of WWW users is not a problem. Approx.30-40 users when problem occurs which should be no problem.
-In the weblog we notice that some requests are taking a very long time or are never ending
Notice this small sequential sample where the second request has ran for 4 minutes:
188.8.131.52 - -
"GET / HTTP/1.1" 200 340
184.108.40.206 - -
"GET /F/YMT22X3GL9K6BQK18LAAEQEUJY781XRJDTQB79BAKIRFD55YDI-03325?func=short-filter-y&start_date=1990&end_date=9999 HTTP/1.1" 503 323
-In apache config we already adjusted the MaxClients but this only delays the problem of reaching the MaxClients
Sample of our current apache config:
# MaxClients 150
#edu 29-9-2006 opgehoogd
-When we look at the www_server logs it looks like the connection is of type 'keep alive' although
in the main config we have 'KeepAlive Off'
Sample of www_server.log:
Header: Keep-Alive <300>
Header: Connection <keep-alive>
Header: Referer <http://aleph.library.uu.nl/>
-The only things changed last months are the servicepack levels and adding SFX connectivity.
We are on servicepacklevel 1712
The MaxRequestsPerChild 30 is too low.
Please try to raise the limit to 1000 and see if it helps.
The MaxClients limit can be higher than 255 by enlarging the HARD_SERVER_LIMIT (TO 512 OR EVEN 1024) in .../include/httpd.h and recompile apache.
- Article last edited: 10/8/2013