From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 18 19:03:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FD3716A4DD for ; Tue, 18 Jul 2006 19:03:39 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 67E9543D70 for ; Tue, 18 Jul 2006 19:03:29 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 12716 invoked by uid 399); 18 Jul 2006 19:03:28 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 18 Jul 2006 19:03:28 -0000 Message-ID: <44BD3086.1010906@FreeBSD.org> Date: Tue, 18 Jul 2006 12:03:34 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: John Von Essen References: <20060718140354.V64880@beck.quonix.net> <44BD2783.1000609@FreeBSD.org> <20060718143105.B64880@beck.quonix.net> In-Reply-To: <20060718143105.B64880@beck.quonix.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: odd behavior in apache 2.0.58 today X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2006 19:03:39 -0000 John Von Essen wrote: > Doug, > > Did some googling and I did find a connection between excessive > CLOSED_WAITS, and hanging apache, and webbots. Some of the IP's I saw in > my netstat were bots too. The problem has something to do with the bot > no longer accepting data, but apache will continue to send it back since > the bot didn't close the connection. Yep, that sounds right to me. > Because my MaxClients was set to 150, my server got so bogged down, that > it actually crashed and I had to power cycle. I moved that down to 75, > which is still more than enough for me, so if it happens again, my > system should remain up in order to restart apache. > > Any ideas if I can tweak apache to prevent this from happening? Maybe > turn-off keepalive? Reducing MaxClients to a sane level is the best bet here. Maybe throw in a monitoring script for system load, and/or apache going insane with too many children. Keepalives are generally a good idea, and for legit clients do more good than harm, so I wouldn't turn them off personally. Doug -- This .signature sanitized for your protection