Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 13132 invoked from network); 26 Feb 2004 22:21:30 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 26 Feb 2004 22:21:29 -0000 Received: (qmail 56247 invoked by uid 500); 26 Feb 2004 22:21:10 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 56193 invoked by uid 500); 26 Feb 2004 22:21:10 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 56172 invoked from network); 26 Feb 2004 22:21:09 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by daedalus.apache.org with SMTP; 26 Feb 2004 22:21:09 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AwTsZ-0006uR-00 for ; Thu, 26 Feb 2004 23:21:15 +0100 Received: from p508055f4.dip.t-dialin.net ([80.128.85.244]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu Feb 26 22:21:15 2004 Received: from ahuxley by p508055f4.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu Feb 26 22:21:15 2004 X-Injected-Via-Gmane: http://gmane.org/ To: dev@httpd.apache.org From: Alexis Huxley Subject: Re: "(97)Address family not supported by protocol" causes "disk ticking"? Date: Thu, 26 Feb 2004 22:21:11 +0000 (UTC) Organization: None Lines: 62 Message-ID: References: <20040223110929.GA32314@redhat.com>

<403E0453.90102@apache.org> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p508055f4.dip.t-dialin.net User-Agent: slrn/0.9.8.0 (Linux) Cache-Post-Path: dione.myth.net!unknown@dione.myth.net X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N >> 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: SetHandler server-status Order Deny,Allow Deny from all Allow from 127.0.0.1 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: StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 > 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