From owner-freebsd-isp Wed Feb 16 0: 0:29 2000 Delivered-To: freebsd-isp@freebsd.org Received: from sblake.comcen.com.au (sblake.comcen.com.au [203.23.236.144]) by builder.freebsd.org (Postfix) with ESMTP id 54B1740C9 for ; Wed, 16 Feb 2000 00:00:25 -0800 (PST) Received: (from aunty@localhost) by sblake.comcen.com.au (8.9.3/8.9.3) id TAA30761 for freebsd-isp@freebsd.org; Wed, 16 Feb 2000 19:04:01 +1100 (EST) (envelope-from aunty) Date: Wed, 16 Feb 2000 19:04:01 +1100 From: aunty To: freebsd-isp@freebsd.org Subject: file descriptors / table is full Message-ID: <20000216190401.A27835@comcen.com.au> Mail-Followup-To: freebsd-isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a BSDI machine about to be converted to FreeBSD, and a FreeBSD machine, doing similar tasks. All day the BSDI machine has been complaining about file descriptors and and file table full, and getting load averages up around 66 for brief periods. (Yes, this is still BSDI but bear with me.) Its kernel has only maxusers 64 which might be a little lean but it has been happy that way for years. Ho hum, I thought, it's old and its days are numbered on one hand, and the new FreeBSD box will wash these mysteries away. I forgot to touch wood. Now suddenly the other machine that is already running FreeBSD starts doing the same thing: Feb 16 18:08:18 hostname sendmail[28442]: SAA28262: SYSERR(UID0): queueup: cannot create queue temp file tfSAA28262, uid=0: Bad file descriptor Feb 16 18:08:56 hostname sendmail[22196]: NOQUEUE: SYSERR(UID0): fill_fd: disconnect: fd 0 not open: Bad file descriptor and complains about all sorts of things like: bash2-2.03$ sudo mkdir holdit Password: sudo: no passwd entry for root! bash2-2.03$ sudo mkdir holdit /usr/libexec/ld-elf.so.1: Cannot open "/usr/lib/libcrypt.so.2" Hmmm, I thought it should have been looking for libdescrypt! And Feb 16 18:19:17 hostname inetd[187]: accept (for pop3): Too many open files in system Feb 16 18:19:18 hostname /kernel: file: table is full Feb 16 18:19:18 hostname sendmail[23967]: RAA23967: SYSERR(UID0): Cannot reopen dfRAA23967: Too many open files in system Its kernel has maxusers set to 128 and it does no more work than the other machine. ISTR maxusers is the usual solution to these things. Could it need to be even higher, or should I be looking elsewhere? I've noticed both machines have large mail queues which they're trying to empty, with hundreds of sendmail processes sitting around for hours. It's been a long day, I can't get to any of the mail archive locations, and the causes and the symptoms are getting a rather muddled here. Can someone help me see the right places to look for clues? -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message