Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of sweetwatergeek@googlemail.com
 designates 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=KCDcg3zO4y6zXTMv3z8s4ZPkTf3Capc9QmB2dvLTtV9RXD1kSNov0DAjWUNtF24YkYoaB3aOag0A22qqSbdKD+P64ZWlavxa2GbJK4Zgn8/F76r0LMu+Q2jY44s+1CM3VmY4fa0BIvENWiIjwDY/z7UvW2jnRZzNcLLgcFM/D2s=
Message-ID: <787fc380704261115o5d5bc703w75d0803768c0abd0@mail.gmail.com>
Date: Thu, 26 Apr 2007 19:15:14 +0100
From: Martijn <sweetwatergeek@googlemail.com>
To: users@httpd.apache.org
In-Reply-To: <e498c1660704231101p300ae3d7yc902061e0bb65e05@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <787fc380704231015q1c187965kc6a25c90e0b7d3f8@mail.gmail.com>
	 <e498c1660704231021k3f17803bu729f75438003698b@mail.gmail.com>
	 <787fc380704231055i305d3424ua87a85e028dc8b33@mail.gmail.com>
	 <e498c1660704231101p300ae3d7yc902061e0bb65e05@mail.gmail.com>
Subject: Re: [users@httpd] send mmap timed out

Sorry for taking so long to reply. I had given the problem a lower
priority, assuming (hoping) it was just one of these mysterious
incidents that only occurs once, when -of course- it happened again.
And -of course- again when I wasn't looking.

> Was this just a denial-of-service attack? Did you use a tool like
> netstat to identify the client connections and track down the origin?

No. I have scrutinized the access and error log files several times,
and I don't see anything suspicious: no sudden increase of traffic, no
increase in requests to specific files, not even more errors than
usual. (Apart from the one in the subject, but I've started to become
more convinced that that isn't the problem. Today, it had occurred
only once just before the problems started.)

Only the number of httpd processes increases suddenly: I have been
monitoring the number of processes on a minute by minute basis, and it
really is normal one minute and at its maximum the next one. I had
been thinking it might be an infinite loop somewhere in a script, but
then why would this script be called so many times at once? And why
doesn't the error occur most of the time? And why doesn't Apache
realise that there is a problem and 'kill' some processes itself?

Questions.. questions... and I realise I probably am not giving a lot
of clues that might lead to a solution. But really, if only I had such
clues...

But perhaps someone here knows what it could be. And if not, thanks
for your time anyway. :)

Martijn.

PS a little bit form httpd.conf:

Timeout 300

KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimeout 5

MinSpareServers 25
MaxSpareServers 30
StartServers 30
MaxClients 85
MaxRequestsPerChild 10000

(I just realised that I had changed MaxClients fro 75 to 85 the other
day -and restarted apache twice since- but the number of processes
still doesn't get higher than 75. Weird.)

---------------------------------------------------------------------
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