Date: Thu, 20 Jan 2000 15:18:43 -0500 From: "bsdnews" <bsdnews@trigger.net> To: <andrew@pubnix.net>, "Bill Vermillion" <bill@bilver.magicnet.net> Cc: <freebsd-isp@FreeBSD.ORG> Subject: Re: curious kernel log messages Message-ID: <000d01bf6383$8c6cf640$cc1232cc@trigger.net> References: <Pine.BSF.4.21.0001201347150.42912-100000@guardian.fortress.org>
next in thread | previous in thread | raw e-mail | index | archive | help
MAXUSERS is set to 128. The system is a p2-350, 2 8GIG Ultra2 SCSI drives, 128 RAM (300 swap), and an fxp nic. It runs low load apache, named, sendmail (medium to high load), delegated, squid, and radiusd. Would a setting of 128 in this case be insufficient? Also some suggested doing a 'fstat -f /var' command and searching for large open files. This is the largest open file I have found. root radiusd 297 1 /var 7962 -rw-r----- 288927657 w root radiusd 294 text /var 7964 -rwx------ 28903 r root radiusd 294 1 /var 7962 -rw-r----- 288927657 w Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/da1s1g 3175193 1727393 1193785 59% 15667 777931 2% /var Could this cause a problem? For some reason the log does not provide information on what file or filesystem is being effected. Thanks. > Actually, you might have run out of open file handles in the kernel. > This is directly affected by the MAXUSERS setting which if not defined is > derived from the number of users setting in the kernel using the following > forumula > > MAXFILES = 2 * (20 + 16 * MAXUSERS) > > See /sys/conf/param.c for how all this stuff is calculated. > > On Thu, 20 Jan 2000, Bill Vermillion wrote: > > > On Thu, Jan 20, 2000 at 01:06:37PM -0500, Thus Spake bsdnews: > > > > > Yes I have, Just this morning I was reading the daily output logs, > > > and I got a LOT of this: > > > > > file: table is full > > > file: table is full > > > file: table is full > > > .... > > > > > Yet, all the filesystems have more then enough space left. If > > > someone has an answer to this, please let me know. > > > > I've seen this and then found I had no problem later. I think it > > was a cron job that ran out of space, and when it aborted it > > cleaned up after itself. > > > > Bill > > -- > > Bill Vermillion bv @ wjv.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isp" in the body of the message > > > > --- > Andrew Webster FULL SERVICE ISP > President http://www.pubnix.net > PubNIX Inc. Access: PPP - SHELL - UUCP - VPN - ... > P.O. Box 147 Hosting: WWW - Email - DB - Your Servers - ... > C.S.L. QC H4V 2Y3 tel: 514-990-5911 fax: 514-990-9443 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > 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?000d01bf6383$8c6cf640$cc1232cc>