From owner-freebsd-stable@FreeBSD.ORG Wed May 2 03:00:18 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 73ADD16A401 for ; Wed, 2 May 2007 03:00:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id 34D3913C468 for ; Wed, 2 May 2007 03:00:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so1884199ana for ; Tue, 01 May 2007 20:00:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=FiFZ+KYbnD2Tw0IxjVvXMJ7dnm3gvRrmj2JllQNmrM/oWF5FhV7X0IXasDHRKeL3Jw6XtjXVrOVJvoYCFd9slHxdosu8zHuNIFDLiVeRa9jCErCeE3+JJlyul2P+vM8i/R73XeoXV/xyIBIDeyMrnovTIKn1TfHqz4dSe8Xsok8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=rnvj04RaJM43t2qNEkqHs4SwIEytCkBG+F96OHZY9eAJWlEw2hRBBIlMdzrM01J4DF7uyl8CxN+Z8LVa70pPQ4DwJLzqqltXEbnw1Jnht6y5QrSvIig3mOl5IDI255oIkGiTuniqGjyncfjAAhTvhQUGbjRwkwUGpeTCGwxY+R4= Received: by 10.100.34.16 with SMTP id h16mr116091anh.1178074817309; Tue, 01 May 2007 20:00:17 -0700 (PDT) Received: by 10.100.197.3 with HTTP; Tue, 1 May 2007 20:00:17 -0700 (PDT) Message-ID: Date: Wed, 2 May 2007 11:00:17 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Marc G. Fournier" In-Reply-To: <366565EAE2F989935287015E@ganymede.hub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <366565EAE2F989935287015E@ganymede.hub.org> X-Google-Sender-Auth: 9440b7aa43b455e0 Cc: freebsd-stable@freebsd.org Subject: Re: What triggers "No Buffer Space Available"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2007 03:00:18 -0000 On 01/05/07, Marc G. Fournier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I'm still being hit by this one ... more frequently right now as I had to move > a bit more stuff *onto* that server ... I'm trying to figure out what I can > monitor for a 'leak' somewhere, but the only thing I'm able to find is the > whole nmbclusters stuff: > > mars# netstat -m | grep "mbuf clusters" > 130/542/672/25600 mbuf clusters in use (current/cache/total/max) > > the above is after 26hrs uptime ... > > Is there something else that will trigger/generate the above error message? It doesn't panic whe it happens, no? I'd check the number of sockets you've currently got open at that point. Some applications might be holding open a whole load of sockets and their buffers stay allocated until they're closed. If they don't handle/don't get told about the error then they'll just hold open the mbufs. (I came across this when banging TCP connections through a simple TCP socket proxy and wondered why networking would lock up. Turns out FreeBSD-6 isn't logging the "please consider raising NMBCLUSTERS" kernel message anymore and I needed to do exactly that. Killing the proxy process actually restored network connectivity.) Adrian -- Adrian Chadd - adrian@freebsd.org