From owner-freebsd-performance@FreeBSD.ORG Thu Jul 17 03:49:45 2003 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 860CA37B401 for ; Thu, 17 Jul 2003 03:49:45 -0700 (PDT) Received: from spf13.us4.outblaze.com (205-158-62-67.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id E10EE43F75 for ; Thu, 17 Jul 2003 03:49:44 -0700 (PDT) (envelope-from jwest254@mail.com) Received: from 205-158-62-68.outblaze.com (205-158-62-68.outblaze.com [205.158.62.68]) by spf13.us4.outblaze.com (Postfix) with QMQP id D2951181E419 for ; Thu, 17 Jul 2003 10:49:44 +0000 (GMT) Received: (qmail 71745 invoked from network); 17 Jul 2003 10:49:44 -0000 Received: from unknown (HELO ws1-8.us4.outblaze.com) (205.158.62.59) by 205-158-62-153.outblaze.com with SMTP; 17 Jul 2003 10:49:44 -0000 Received: (qmail 99328 invoked by uid 1001); 17 Jul 2003 10:49:44 -0000 Message-ID: <20030717104944.99327.qmail@mail.com> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [193.120.103.96] by ws1-8.us4.outblaze.com with http for jwest254@mail.com; Thu, 17 Jul 2003 05:49:44 -0500 From: "James West" To: "Terry Lambert" Date: Thu, 17 Jul 2003 05:49:44 -0500 X-Originating-Ip: 193.120.103.96 X-Originating-Server: ws1-8.us4.outblaze.com cc: freebsd-performance@freebsd.org Subject: Re: Major problem with "No buffer space available" errors X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 10:49:45 -0000 Added up all the sendq and recvq columns in a netstat -na output gives me almost always < 150 and i'm still getting almost constant no buffer space errors. The NIC was replaced only five minutes ago and the problem still persists. [root@flower] (/home/james): ping 127.0.0.1 ping: socket: No buffer space available [root@flower] (/home/james): ping 127.0.0.1 ping: socket: No buffer space available [root@flower] (/home/james): ping 127.0.0.1 ping: socket: No buffer space available [root@flower] (/home/james): ifconfig ifconfig: socket: No buffer space available [root@flower] (/home/james): ifconfig ifconfig: socket: No buffer space available [root@flower] (/home/james): dmesg | grep fxp0 fxp0: port 0xb000-0xb03f mem 0xda800000-0xda81ffff,0xdb000000-0xdb000fff irq 12 at device 16.0 on pci0 fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0x50a0 fxp0: EEPROM checksum @ 0x3f: 0xca9a -> 0xca9c fxp0: Ethernet address 00:02:b3:48:50:2a ----- Original Message ----- From: Terry Lambert Date: Wed, 16 Jul 2003 22:41:32 -0700 To: James West Subject: Re: Major problem with "No buffer space available" errors > James West wrote: > > I'm having huge problems with "No buffer space available" errors. I've > > increased MAXUSERS to 512 in the kernel, recompiled, rebooted and the > > sysctl values below show that everything is up'ed to the max. > > Historically, the most common cause of this message has been an > interface you were actively feeding data going down. Most commonly, > this occurs in the use of UDP and ICMP protocols (e.g. "ping") out a > downed interface, since they are not constrained by your sendspace > settings, which apply to TCP (they will basically permit you to use > all your buffer in the attempt). > > So the questions to answer are: > > 1) Are you using a lot of ICMP (e.g. ping, traceroute, RIP, etc.)? > > 2) Are you using a lot of UDP (e.g. Linux NFS clients using UDP > mounts and an rsize or wsize larger than the MTU would permit > to fit in a single UDP packet)? > > Other than that, you should "netstat -an" and add up the contents of > the SendQ/RecvQ columns. It's possible that, in fact, you *are* > running out of buffer space. For the default of 64K, you would need > 2G of RAM dedicated to nothing but mbufs (not including headers!) to > support only 32,768 simultaneous connections without mbuf overcommit. > > Dropping the sndspace/rcvspace paramaters back to their pre-bump-up > defaults will double the number of connections for the same amount > of RAM. > > -- Terry > _______________________________________________ > freebsd-performance@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-performance > To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org" -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers