Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!yarrina.connect.com.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!gatech!willis.cis.uab.edu!nntp.msstate.edu!hobbes.gtlug.org!simmons
From: simmons@aris.com (David Simmons)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: sendto() buffer exhausted in 2.1.0-RELEASE...
Date: 19 Jan 1996 20:01:55 GMT
Organization: Aris Technology, Inc.
Lines: 26
Message-ID: <4dotbj$2fo@NNTP.MsState.Edu>
NNTP-Posting-Host: hobbes.gtlug.org
I've recently had a server running FreeBSD 2.1.0-RELEASE
fail because the named locked up (and this machine depends
on its named for name resolution). A ktrace revealed that
the sendto() system call did not have access to buffer space:
10273 named CALL sendto(0x3,0xefbfd034,0x90,0,0,0)
10273 named RET sendto -1 errno 55 No buffer space available
Which the sendto(2) man page describes as:
[ENOBUFS] The system was unable to allocate an internal buffer. The
operation may succeed when buffers become available.
I had to reboot the machine to clear up the problem. What would cause
the kernel buffers to become exhausted? Is there a known bug or memory
leak in 2.1.0-RELEASE that would lead to this? We just upgraded the
kernel to 2.1.0-RELEASE recently.
Thanks in advance for any insight...
David
--
David Simmons, simmons@aris.com
Internet Consultant, Aris Technology, Inc.
Visit my home page! http://www.aris.com/~simmons/