From owner-freebsd-stable Thu Dec 6 7: 4:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bilver.wjv.com (spdsl-033.wanlogistics.net [63.209.115.33]) by hub.freebsd.org (Postfix) with ESMTP id 5173337B41A for ; Thu, 6 Dec 2001 07:04:16 -0800 (PST) Received: (from bv@localhost) by bilver.wjv.com (8.11.6/8.11.6) id fB6F4At12919 for stable@FreeBSD.ORG; Thu, 6 Dec 2001 10:04:10 -0500 (EST) (envelope-from bv) Date: Thu, 6 Dec 2001 10:04:10 -0500 From: Bill Vermillion To: stable@FreeBSD.ORG Subject: Re: stable-digest V5 #360 Message-ID: <20011206100410.C12127@wjv.com> Reply-To: bv@wjv.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from owner-freebsd-stable-digest@FreeBSD.ORG on Thu, Dec 06, 2001 at 06:49:30AM -0800 Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Re: Whats with this -> sendto: No buffer space available > Date: Thu, 06 Dec 2001 18:28:48 +1100 > From: Kal Torak > Subject: Re: Whats with this -> sendto: No buffer space available > > Doug Silver wrote: > > > It happens all the time on one of my nameservers, but only when amanda is > > trying to back it up. Then it says this: > > > > > >>Dec 4 23:00:43 HOST syslogd: sendto: No buffer space available > >>Dec 5 00:00:36 HOST syslogd: sendto: No buffer space available > >> > > > > It does not affect the machine other than this message. > > Hmmm, no affect??? > > When ever I get this message the machine can no longer send any data > to the network on that interface... The interface has to be reset... > > Perhaps the cause of your message is due to lack of mbufs for the load > its getting, you should probably increase them... > > The problem the rest of us have is different... I am almost 100% sure > this is being caused by a problem upstream, the data cant get out so > the sendto buffer fills and seems to lock up the interface... I have a > feeling this may be specific to PPP connections, anyone finding this > locks there interface on a non PPP connection??? (pppoe is still ppp > could this even be specific to pppoe??) > > Anyway to my way of thinking this is an error in the handeling of this > kind of situation and needs to be looked at... Is there anything that > I can log or dump next time this happens that would be helpfull in fixing > this??? Well my no buffer space available came from a DSL. Not pppoe. It's actually ppoa - BUT - all that is handled by the DSL modem. I have private IPs. I had a WinME machine doing something, I had this machine doing something, and my other BSD machine was performing a DL from an FTP site in Europe or possibly to one of my servers. [My DSL is 512Kb down while the servers I admin are 100Mbit uplinks into an OC192 backbone and I often DL to there and then just perform a final transfer to here as I contol both ends of the link and and wont have delays/timeouts] The machine with the FTP got the no buffer space available and it and this machine are running 4.4. This machine was just recently reloaded with 4.4 from CD as I stupidly trashed my HD by accident. Since the machine that died was performing pure IP to IP [as it looked to itself] there was no pppoe involved. Bringing the interface down and backup fixed it. If it makes any difference the image > > > End of stable-digest V5 #360 > **************************** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with unsubscribe freebsd-stable-digest in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message