Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!feeder.chicago.cic.net!chi-news.cic.net!news.sprintlink.net!news-peer.sprintlink.net!howland.erols.net!feed1.news.erols.com!news.ecn.uoknor.edu!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!news.bri.connect.com.au!fjholden.OntheNet.com.au!news From: Tony Griffiths <tonyg@OntheNet.com.au> Newsgroups: comp.unix.bsd.freebsd.misc Subject: named : socket(SOCK_DGRAM): Too many open files - exiting Date: Wed, 13 Nov 1996 14:45:17 +1000 Organization: On the Net (ISP on the Gold Coast, Australia) Lines: 15 Message-ID: <3289525D.258A@OntheNet.com.au> Reply-To: tonyg@OntheNet.com.au NNTP-Posting-Host: swanee.nt.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (WinNT; I) We have a problem with named on FreeBSD 2.1.5-RELEASE. The machine in question is a virtual Web server with about 66 domains. It boots correctly but if we add a new domain and "kill -HUP" named, it fails to open it's UDP sockets and gives the above error. I've looked at the number of open files with fstat and it is nowhere near the system limit per process or system wide. The only thing that fixes the problem is a reboot. The maxusers config parameter is set to 64 so the maximum open files is > 2048. fstat reports only about 590-600 open files including the 4 UDP sockets open by named. I've looked at the Filesystem code that allocates a new FD and which can return an EMFILE error but cannot see why it might be failing! Anyone have any clues as to what the problem might be? Tony