Re: kern.maxfiles questions
On Dec 29, 2003, at 7:24 AM, Lowell Gilbert wrote: Is there some way to find out what's tying up the file descriptors? fstat(1) Of course. I had been thinking of that in terms of files, not file handles. D'oh. -- Paul Beard paulbeard [at] mac.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern.maxfiles questions
paul beard <[EMAIL PROTECTED]> writes: > Is there some way to find out what's tying up the file descriptors? fstat(1) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern.maxfiles questions
Some updates to this. The machine was unresponsive this AM so I had to reboot it. I'm used to 90-100 day uptimes (as the power company permits) so this is quite unusual. On Dec 27, 2003, at 11:03 PM, paul beard wrote: [/usr/home/paul]:: sysctl kern.openfiles kern.maxfiles kern.openfiles: 257 kern.maxfiles: 4040 I raised the kern.maxfiles to 16383 and am monitoring it with mrtg (http://www.paulbeard.org/mrtg/red/red-openfiles.html). Already it's at almost 3000 (from less than 300 when I first noted it), so I assume I'll hit 4040 before too long. and on further examination I am finding some swap shortages (this machine has 512 Mb of real memory but only the same amount of swap). I actually only have 256 Mb of RAM with a half gig swap partition. I added another 512 Mb swap file and I am monitoring swap vs real mem usage as well (http://www.paulbeard.org/mrtg/red/red-mem.html). if this is all I need to do, I guess that's OK, but I'm still not sure why it became an issue all of a sudden. Is there some way to find out what's tying up the file descriptors? -- Paul Beard paulbeard [at] mac.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kern.maxfiles questions
I'm still having some issues with file descriptors being used up. Symptomatically, my http listener will become sluggish and some cgi processes I use will time out. The logs have a raft of these messages: Dec 27 22:46:13 red /kernel: kern.maxfiles limit exceeded by uid 80, please see tuning(7). Dec 27 22:47:12 red /kernel: kern.maxfiles limit exceeded by uid 1004, please see tuning(7). I can't even query sysctl, but after stopping httpd and postfix (the processes being run by those UIDs) I can finally get this information. [/usr/home/paul]:: sysctl kern.openfiles kern.maxfiles kern.openfiles: 257 kern.maxfiles: 4040 and on further examination I am finding some swap shortages (this machine has 512 Mb of real memory but only the same amount of swap). what tunables can be twiddled, assuming swap doesn't solve this? FreeBSD red.paulbeard.org 4.9-RELEASE FreeBSD 4.9-RELEASE #3: Sun Dec 21 14:01:26 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/RED i386 -- Paul Beard paulbeard [at] mac.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"