From owner-freebsd-questions Thu Apr 22 18:54:22 1999 Delivered-To: freebsd-questions@freebsd.org Received: from WEBBSD1.turnaround.com.au (webbsd1.turnaround.com.au [203.39.138.49]) by hub.freebsd.org (Postfix) with ESMTP id 4C3AF14CF8 for ; Thu, 22 Apr 1999 18:54:18 -0700 (PDT) (envelope-from A_Johns@TurnAround.com.au) Received: from TurnAround.com.au (dhcp64.turnaround.com.au [192.168.1.64]) by WEBBSD1.turnaround.com.au (8.8.7/8.8.7) with ESMTP id MAA16435; Fri, 23 Apr 1999 12:00:48 +1000 (EST) (envelope-from A_Johns@TurnAround.com.au) Message-ID: <371FD257.9C204682@TurnAround.com.au> Date: Fri, 23 Apr 1999 11:52:23 +1000 From: Andrew Johns Organization: TurnAround Solutions P/L X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Ronald F. Guilmette" Cc: questions@FreeBSD.ORG Subject: Re: PLEASE HELP! Still need help re: No buffer space available References: <20875.924290899@monkeys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ronald F. Guilmette" wrote: > > HELP! > > Nobody ever sent me *any* response to the following query. > > I am desperate for an answer. > > The same exact problem has struck again... `No buffer space available' when > trying to open a socket, and as a result, a critical application crashes. > > This time something new also appears to have happened at the around the same > time, i.e. the kernel message log seems to have been filled up with a TON > of messages that all say: > > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > rtfree: 0xf591a700 not freed (neg refs) > > What the devil goes on here?? > > This is all happening on a stock FreeBSD 2.2.8 system. (Ain't that supposed > to be ``stable''?) > > ------- Forwarded Message > > To: questions@freebsd.org > Subject: No buffer space available > From: "Ronald F. Guilmette" > Date: Sat, 03 Apr 1999 14:35:21 -0800 > Message-ID: <20431.923178921@monkeys.com> > Sender: rfg@monkeys.com > > I have a program that opesn a LOT of sockets simultaneously. > > It occasionally dies because it gets a `No buffer space available' error > when trying to create yet another socket. > > I have already reconfigured my kernel (2.2.8) so that I have maxusers set > to 192 and also NMBCLUSTERS set to 24576. > > OK, so what ELSE do I need to do in order to make this error go away? > > What is the name of the kernel parameter that determines how much space > the kernel will use (at a maximum) for socket buffers? > > P.S. I really don't think I am anywhere near to running out of physical > memory. The box in question has just ooodles and oodles of it. > > ------- End of Forwarded Message What requirement is there to open a large number of sockets simultaneously? Can the design be altered so that this is not a problem? (I know it seems a stupid question for me to ask, but I need a handle on what you're trying to achieve..) Also, you say "stock 2.2.8 system", but you've not included whether it was RELEASE, STABLE or CURRENT...you've recompiled the kernel, what else have you done? What other details are available - you say you *think* you're not running out of memeory - how do you know this to be true? Basically, more info required. -- Regards | _/\_/\ Andrew Johns BSc (Comp Sci) | / \ TurnAround Solutions Pty Ltd | \_...__/ http://www.turnaround.com.au/ | \/ "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message