From owner-freebsd-current@FreeBSD.ORG Thu Sep 20 21:56:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F4CC16A420; Thu, 20 Sep 2007 21:56:39 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from proxypop1.sarenet.es (proxypop1.sarenet.es [194.30.0.99]) by mx1.freebsd.org (Postfix) with ESMTP id 1E2CD13C44B; Thu, 20 Sep 2007 21:56:39 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from [127.0.0.1] (matahari.sarenet.es [192.148.167.18]) by proxypop1.sarenet.es (Postfix) with ESMTP id CDE825D49; Thu, 20 Sep 2007 13:51:33 +0200 (CEST) In-Reply-To: References: <5870F83F-7174-47AA-98AE-C1DE8972E0C8@SARENET.ES> <613318C3-6B66-4758-A0D4-97405D6A1914@SARENET.ES> <46F23166.8070908@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4C4A3C06-A6F3-41B1-BE53-F04369CD4F8D@SARENET.ES> Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Thu, 20 Sep 2007 13:51:35 +0200 To: Borja Marcos X-Mailer: Apple Mail (2.752.2) Cc: Kris Kennaway , freebsd-current@freebsd.org, Ivan Voras Subject: Re: Memory allocation problems (ZFS/NFS/amd64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2007 21:56:39 -0000 On 20 Sep 2007, at 12:02, Borja Marcos wrote: > I've just tried using the echo service from inetd, and the server > is keeping 1024 established > connections without that error. I just don't understand why this > can fail with Apache, but it seems it's an issue with -current, as > we have a similar setup with 6.2(i386), same hardware, and it works. Here's what I've found out. Apache was confgured by a different person, and I didn't notice that the MaxClients parameter was set too low (159). Setting it up to a high value (1024) has made those errors disappear. So that "memory limit" was actually that the system was dropping connection requests from the listen queue. The error message is quite looks misleading to me. At least I had never seen it, so it caught me by surprise. Sorry about the confusion. I will go on doing tests and let you know the result. Borja. ---------------- "The thing he realised about the windows was this: because they had been converted into openable windows after they had first been designed to be impregnable, they were, in fact, much less secure than if they had been designed as openable windows in the first place." Douglas Adams, "Mostly Harmless"