httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer M. Canavan" <rainer.cana...@sevenval.com>
Subject Re: [users@httpd]
Date Thu, 19 Mar 2015 11:11:24 GMT

On Mar 19, 2015, at 01:11 , el kalin <kalin@el.net> wrote:

[…]
> my guess is that the "dummy" connections (since they don't have their own process attached
to them) are there because some of the other processes that do show in ps ask for those at
various stages. is it true? how would i know which one asked? does it matter?

The OPTIONS-Request you see in that list is merely the last request that has been processed
by that process. The processes are not actually busy, if they were their states would typically
be "R" "W" or "L", and certainly not "."

> i've experienced some issues where the (open?!) "dummy" connections become so many that
the server stops responding but the ps -auwx | grep httpd shows just 10 processes or so running.
after restart everything goes back to normal. except i'm not always there to restart… 


If the server absoluteley does not respond because it is not allowed to start more servers
(or threads), try killing one worker child and requesting the /ServerStatus. 

> so one though i had about this is that in my httpd-mpm file the only loaded module is
mpm_prefork_module. which has this in it's scope (default values):
> 
>     StartServers             5
>     MinSpareServers          5
>     MaxSpareServers         10
>     MaxRequestWorkers      250
>     MaxConnectionsPerChild   0
> 
> is it reasonable to believe that MaxConnectionsPerChild should have some reasonable limit?
will this control how many "dummy" connections are kept alive?


The ServerStatus output below seems correct for the configuration above, since there are exaclty
10 spare children idling. They probably won't ever be reaped, unless you set MaxConnectionsPerChild
to some number > 0, in which case they will die after processing that number of requests.
On a server that is idle most of the time, that may take a while, since requests are distributed
round robin among the idle children.

> 
> 27-0	-	0/0/3	. 	0.00	2895	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 28-0	-	0/0/10	. 	0.02	2829	0	0.0	0.00	0.85 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 29-0	-	0/0/2	. 	0.00	2893	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 30-0	-	0/0/2	. 	0.00	2884	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 31-0	-	0/0/2	. 	0.00	2894	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 32-0	-	0/0/8	. 	0.03	2719	0	0.0	0.00	0.50 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 33-0	-	0/0/1	. 	0.00	2890	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 34-0	-	0/0/1	. 	0.00	2869	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 35-0	-	0/0/1	. 	0.00	2888	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0
> 36-0	-	0/0/1	. 	0.00	2882	0	0.0	0.00	0.00 	127.0.0.1	my.domain.com:80	OPTIONS * HTTP/1.0



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


Mime
View raw message