You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Jan Houtsma <ja...@houtsma.net> on 2003/10/18 11:28:31 UTC

[users@httpd] Hanging/Remaining httpd child processes > MaxSpareServers

Hello,

It looks like my apache webserver doesn't kill off unused child processes
above
the MaxSpareServers number. I hope someone can confirm that the following is

*not* normal or maybe someone can confirm that it is normal behaviour and
that 
i simply don't understand (very well possible as well).

System: RedHat 9 / glibc-2.3.2-27.9 / httpd-2.0.40-21.5
=======

httpd.conf:
=========== 
<IfModule prefork.c>
StartServers       8
MinSpareServers    5
MaxSpareServers   20
MaxClients        60
MaxRequestsPerChild  1000
</IfModule>

As i type this i have 39 httpd child processes. There are *no* connections 
anymore since yesterday (i closed ports 80 and 443). Shouldn't there be at 
most 20 child processes if there are no connections?

The worst thing is that if MaxClients has been reached the webserver even
doesn't respond anymore (also nothing written to the logfiles anymore).

I am afraid this is caused by 

	http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90036

because i also had a problem with smbmount not killing a child process 
correctly which has been identified as a glibc bug (see the link above).

Maybe apache suffers the same because of this glibc bug?
Is there anybody with RedHat 9 who can confirm this?

Thanks,

-- 
Jan Houtsma


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org