Date: Thu, 17 Jul 2003 05:49:44 -0500 From: "James West" <jwest254@mail.com> To: "Terry Lambert" <tlambert2@mindspring.com> Cc: freebsd-performance@freebsd.org Subject: Re: Major problem with "No buffer space available" errors Message-ID: <20030717104944.99327.qmail@mail.com>
next in thread | raw e-mail | index | archive | help
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: <Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet> 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 <tlambert2@mindspring.com> Date: Wed, 16 Jul 2003 22:41:32 -0700 To: James West <jwest254@mail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030717104944.99327.qmail>