Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Feb 2000 19:04:01 +1100
From:      aunty <aunty@comcen.com.au>
To:        freebsd-isp@freebsd.org
Subject:   file descriptors / table is full
Message-ID:  <20000216190401.A27835@comcen.com.au>

next in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000216190401.A27835>