httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexis Huxley <ahux...@gmx.net>
Subject Re: "(97)Address family not supported by protocol" causes "disk ticking"?
Date Thu, 26 Feb 2004 22:21:11 GMT
>> 	Process 1008 attached - interrupt to quit
>> 	select(0, NULL, NULL, NULL, {0, 620000}) = 0 (Timeout)
>> 	write(6, "!", 1)                        = 1
>> 	socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = -1 ENOSYS (Function not implemented)
>> 	socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = -1 ENOSYS (Function not implemented)
>> 	socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family not
supported by protocol)
>> 	gettimeofday({1077743877, 15040}, NULL) = 0
>> 	write(7, "[Wed Feb 25 22:17:57 2004] [warn"..., 114) = 114
>> 	waitpid(-1, 0xbffffa00, WNOHANG|WUNTRACED) = 0
>> 	select(0, NULL, NULL, NULL, {1, 0})     = 0 (Timeout)
>> 	write(6, "!", 1)                        = 1
>> 	socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = -1 ENOSYS (Function not implemented)
>
>> 	.....

> aren't responding to the pipe of death.  Could it be that network traffic is 
> totally dried up during these periods?  or could the child processes be in the 

By "totally dried up" do you mean is the host getting fewer requests?
This machine gets about 20-30 requests per hour usually. 

> middle of some long running request?  server-status with ExtendedStatus On would 
> help answer those questions.

Okay, I added this to httpd.conf:

	<Location /server-status>
	    SetHandler server-status
	    Order Deny,Allow
	    Deny from all
	    Allow from 127.0.0.1
	</Location>
	ExtendedStatus on

and restarted httpd.

>  From the ps, it looks like you are using the prefork mpm...is that correct?

As per out-of-the-box httpd.conf, I have:

	<IfModule prefork.c>
	    StartServers          5
	    MinSpareServers       5
	    MaxSpareServers      10
	    MaxClients          150
	    MaxRequestsPerChild   0
	</IfModule>

> I'm guessing you hear the disk ticking once a second like clockwork when this 
> happens.

Exactly.

>> I'll post a bug on Saturday either way unless someone suggest otherwise. 
>
> sure, might as well.

Okay, now I'll wait till Sunday evening or the next occurence, whichever
is first, in order to try to get the info you requested into the bug
report at the same time.

Alexis


Mime
View raw message