From owner-freebsd-current Sun May 31 23:56:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12737 for freebsd-current-outgoing; Sun, 31 May 1998 23:56:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12715 for ; Sun, 31 May 1998 23:56:24 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.0.Beta5/8.9.0.Beta5) id IAA16317; Mon, 1 Jun 1998 08:54:17 +0200 (SAT) From: John Hay Message-Id: <199806010654.IAA16317@zibbi.mikom.csir.co.za> Subject: Re: mbuf cluster problem continues!! In-Reply-To: <199806010520.WAA09567@implode.root.com> from David Greenman at "May 31, 98 10:20:10 pm" To: dg@root.com Date: Mon, 1 Jun 1998 08:54:17 +0200 (SAT) Cc: andrew@iaccess.com.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I'm still having the same mbuf cluster problem. I'm running squid with a 14 > >Gig Cache and getting up to 200 connections a second. The problem is that > >mbuf clusters in-use just keeps on rising until it gets to the peak and then > >the whole thing crashes. I've got it set to 22000 at the moment, but last > >time they went up to nearly 10000 before it crashed. Is there a problem > >with leaking mbuf clusters still, or is that what they are supposed to do? > > > >If this has been addressed already and i missed it, i would be glad if > >someone could bring me up to date :) > > I've seen several reports of mbuf leaks in the specific case of running > squid proxy servers. As I don't have anything remotely resembling that in any > configuration I have here, someone else will have to troubleshoot this one. > It's possible that this might actually be a bug in squid rather than in > FreeBSD. I have really no idea; I've not seen any mbuf leaks in any other > networking use of FreeBSD so it is surprising that one would show up when > doing this. Isn't it just the various TCP wait states for old connections that still have to timeout that look like mbuf leaks? Even on my not-so-very-busy squid server there is always some of them hanging around. You can easily see that with "netstat -an". John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message