From owner-freebsd-stable Wed Dec 5 23:28:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id D9F9B37B416; Wed, 5 Dec 2001 23:28:19 -0800 (PST) Received: from [144.137.127.185] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id cbwdaaaa for ; Thu, 6 Dec 2001 18:28:31 +1100 Message-ID: <3C0F1E30.3040508@quake.com.au> Date: Thu, 06 Dec 2001 18:28:48 +1100 From: Kal Torak User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5) Gecko/20011011 X-Accept-Language: en-us MIME-Version: 1.0 To: Doug Silver Cc: Jonathan Hanna , FreeBSD ISP , FreeBSD Stable Subject: Re: Whats with this -> sendto: No buffer space available References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 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??? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message