Re: Too many files open / file: table is full
I had the same issue. increasing the maxuser in the kernel and recompiling was the answer. - Original Message - From: Ruben de Groot [EMAIL PROTECTED] To: aSe [EMAIL PROTECTED] Cc: FreeBSD-Questions [EMAIL PROTECTED] Sent: Monday, February 03, 2003 7:52 AM Subject: Re: Too many files open / file: table is full Hi Gordon, On Sun, Feb 02, 2003 at 06:16:26PM -0500, aSe typed: Recently, one of the machines I help to admin ran into problems and had to be rebooted. The machine uptime was about 40days and one of the techs told me it became unresponsive and any command he typed into term it responded Too many files open. Checking the logs now i see the below at the very same time. It is 4.7-Release, I will be more then happy to post more information if requested. Right now I'm just trying to figure out what happen and how to fix. I know for a fact the 13gb drive had over 7gb free, so is there a setting where I can adjust the number of open files? This is not a matter of diskspace. The kernel holds a fixed length table in memory with all open files. If this table gets full it usually means one of two things: 1) You have a runaway application, opening way too many files. Identify the application and fix or disable it. 2) You're running a kernel with a too low value for maxusers (which, among other things, determines the maximum amount of open files). The default in 4.7-RELEASE is 0, which means: optimize according to amount of memory installed. The default is usually O.K. If not, one option is to simply install more memory. cheers, Ruben Jan 22 21:22:18 Fail /kernel: le: table is full Jan 22 21:22:18 Fail /kernel: file: table is full Jan 22 21:22:18 Fail last message repeated 1450 times Jan 22 21:22:18 Fail /kernel: le: table is full Jan 22 21:22:18 Fail /kernel: file: table is full Thank you, Gordon Keesler [[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Too many files open / file: table is full
At 07:43 AM 2.4.2003 +0100, Ruben de Groot wrote: On Tue, Feb 04, 2003 at 12:16:23AM -0500, aSe typed: This is not a matter of diskspace. The kernel holds a fixed length table in memory with all open files. If this table gets full it usually means one of two things: 1) You have a runaway application, opening way too many files. Identify the application and fix or disable it. 2) You're running a kernel with a too low value for maxusers (which, among other things, determines the maximum amount of open files). The default in 4.7-RELEASE is 0, which means: optimize according to amount of memory installed. The default is usually O.K. If not, one option is to simply install more memory. The machine itself runs several logging applications and things of that nature. I didn't think It was an issue with HD. Nor do I believe its ram, It has 512mb installed, and 256mb of swap. As it stands right now it has 270mb free and hasn't touched the swap. Right now maxusers is set to 6, I didn't realize it would play a role in this instance. You should set maxusers to 0. That way, it will be sized at boot time according to the amount of memory you installed. Jack Stone suggested looking up the number of max open files by doing sysctl kern.maxfiles It returns only 232 which to me seems like a very small number. He also suggested to change it using sysctl -w kern.maxfiles=4160. My question to you is, does maxusers play more of a role then just the max number of open files. In the long run would it be better to just set maxusers to 0 or just change the kern.maxfiles? It does. According to tuning(7): kern.maxusers controls the scaling of a number of static system tables, including defaults for the maximum number of open files, sizing of net- work memory resources, etc. You can set maxusers to 0 by either recompiling your kernel or by setting the value in loader.conf(5) Ruben Yes, the 232 is way too low and setting the max users to 0 in the kernel is recommended. But, as I suggested, if you play with the number by raising it using the command line in the meantime (before new kernel reboot), you will find a point where the problem disappears. I imagine the arbitrary number of 4160 I gave you will work. My servers have 1GB of RAM and higher and the lowest number I have is 8192 and some are at 12000+ (my kernels are set to zero for max users), all ascertained by the system itself. I've seen other settings suggested, but with the 0 max users setting in the kernel using FBSD-4.7 (didn't this start at 4.5?), it should become a non-issue. Fot those using earlier versions, like FBSD-4.4 and below, using max users at 32 seems common unless you have some trouble. Then experimenting with resetting using the command line should take care of it. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Too many files open / file: table is full
At 07:43 AM 2.4.2003 +0100, Ruben de Groot wrote: On Tue, Feb 04, 2003 at 12:16:23AM -0500, aSe typed: This is not a matter of diskspace. The kernel holds a fixed length table in memory with all open files. If this table gets full it usually means one of two things: 1) You have a runaway application, opening way too many files. Identify the application and fix or disable it. 2) You're running a kernel with a too low value for maxusers (which, among other things, determines the maximum amount of open files). The default in 4.7-RELEASE is 0, which means: optimize according to amount of memory installed. The default is usually O.K. If not, one option is to simply install more memory. The machine itself runs several logging applications and things of that nature. I didn't think It was an issue with HD. Nor do I believe its ram, It has 512mb installed, and 256mb of swap. As it stands right now it has 270mb free and hasn't touched the swap. Right now maxusers is set to 6, I didn't realize it would play a role in this instance. You should set maxusers to 0. That way, it will be sized at boot time according to the amount of memory you installed. Jack Stone suggested looking up the number of max open files by doing sysctl kern.maxfiles It returns only 232 which to me seems like a very small number. He also suggested to change it using sysctl -w kern.maxfiles=4160. My question to you is, does maxusers play more of a role then just the max number of open files. In the long run would it be better to just set maxusers to 0 or just change the kern.maxfiles? It does. According to tuning(7): kern.maxusers controls the scaling of a number of static system tables, including defaults for the maximum number of open files, sizing of net- work memory resources, etc. You can set maxusers to 0 by either recompiling your kernel or by setting the value in loader.conf(5) Ruben Thank you! Gordon Keesler [[EMAIL PROTECTED]] BTW, in looking at the tuning(7), it specifically says this about maxfiles. Note the typically a few thousand setting: The kern.maxfiles sysctl determines how many open files the system sup- ports. The default is typically a few thousand but you may need to bump this up to ten or twenty thousand if you are running databases or large descriptor-heavy daemons. The read-only kern.openfiles sysctl may be interrogated to determine the current number of open files on the system. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Too many files open / file: table is full
Hi Gordon, On Sun, Feb 02, 2003 at 06:16:26PM -0500, aSe typed: Recently, one of the machines I help to admin ran into problems and had to be rebooted. The machine uptime was about 40days and one of the techs told me it became unresponsive and any command he typed into term it responded Too many files open. Checking the logs now i see the below at the very same time. It is 4.7-Release, I will be more then happy to post more information if requested. Right now I'm just trying to figure out what happen and how to fix. I know for a fact the 13gb drive had over 7gb free, so is there a setting where I can adjust the number of open files? This is not a matter of diskspace. The kernel holds a fixed length table in memory with all open files. If this table gets full it usually means one of two things: 1) You have a runaway application, opening way too many files. Identify the application and fix or disable it. 2) You're running a kernel with a too low value for maxusers (which, among other things, determines the maximum amount of open files). The default in 4.7-RELEASE is 0, which means: optimize according to amount of memory installed. The default is usually O.K. If not, one option is to simply install more memory. cheers, Ruben Jan 22 21:22:18 Fail /kernel: le: table is full Jan 22 21:22:18 Fail /kernel: file: table is full Jan 22 21:22:18 Fail last message repeated 1450 times Jan 22 21:22:18 Fail /kernel: le: table is full Jan 22 21:22:18 Fail /kernel: file: table is full Thank you, Gordon Keesler [[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Too many files open / file: table is full
At 02:52 PM 2.3.2003 +0100, Ruben de Groot wrote: Hi Gordon, On Sun, Feb 02, 2003 at 06:16:26PM -0500, aSe typed: Recently, one of the machines I help to admin ran into problems and had to be rebooted. The machine uptime was about 40days and one of the techs told me it became unresponsive and any command he typed into term it responded Too many files open. Checking the logs now i see the below at the very same time. It is 4.7-Release, I will be more then happy to post more information if requested. Right now I'm just trying to figure out what happen and how to fix. I know for a fact the 13gb drive had over 7gb free, so is there a setting where I can adjust the number of open files? This is not a matter of diskspace. The kernel holds a fixed length table in memory with all open files. If this table gets full it usually means one of two things: 1) You have a runaway application, opening way too many files. Identify the application and fix or disable it. 2) You're running a kernel with a too low value for maxusers (which, among other things, determines the maximum amount of open files). The default in 4.7-RELEASE is 0, which means: optimize according to amount of memory installed. The default is usually O.K. If not, one option is to simply install more memory. cheers, Ruben In the meantime, you can check your settings on the maxfiles by this command: # sysctl kern.maxfiles ...then, you can change it with this: #sysctl -w kern.maxfiles=4160 (...or whatever works best) Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Too many files open / file: table is full
This is not a matter of diskspace. The kernel holds a fixed length table in memory with all open files. If this table gets full it usually means one of two things: 1) You have a runaway application, opening way too many files. Identify the application and fix or disable it. 2) You're running a kernel with a too low value for maxusers (which, among other things, determines the maximum amount of open files). The default in 4.7-RELEASE is 0, which means: optimize according to amount of memory installed. The default is usually O.K. If not, one option is to simply install more memory. The machine itself runs several logging applications and things of that nature. I didn't think It was an issue with HD. Nor do I believe its ram, It has 512mb installed, and 256mb of swap. As it stands right now it has 270mb free and hasn't touched the swap. Right now maxusers is set to 6, I didn't realize it would play a role in this instance. Jack Stone suggested looking up the number of max open files by doing sysctl kern.maxfiles It returns only 232 which to me seems like a very small number. He also suggested to change it using sysctl -w kern.maxfiles=4160. My question to you is, does maxusers play more of a role then just the max number of open files. In the long run would it be better to just set maxusers to 0 or just change the kern.maxfiles? Thank you! Gordon Keesler [[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Too many files open / file: table is full
On Tue, Feb 04, 2003 at 12:16:23AM -0500, aSe typed: This is not a matter of diskspace. The kernel holds a fixed length table in memory with all open files. If this table gets full it usually means one of two things: 1) You have a runaway application, opening way too many files. Identify the application and fix or disable it. 2) You're running a kernel with a too low value for maxusers (which, among other things, determines the maximum amount of open files). The default in 4.7-RELEASE is 0, which means: optimize according to amount of memory installed. The default is usually O.K. If not, one option is to simply install more memory. The machine itself runs several logging applications and things of that nature. I didn't think It was an issue with HD. Nor do I believe its ram, It has 512mb installed, and 256mb of swap. As it stands right now it has 270mb free and hasn't touched the swap. Right now maxusers is set to 6, I didn't realize it would play a role in this instance. You should set maxusers to 0. That way, it will be sized at boot time according to the amount of memory you installed. Jack Stone suggested looking up the number of max open files by doing sysctl kern.maxfiles It returns only 232 which to me seems like a very small number. He also suggested to change it using sysctl -w kern.maxfiles=4160. My question to you is, does maxusers play more of a role then just the max number of open files. In the long run would it be better to just set maxusers to 0 or just change the kern.maxfiles? It does. According to tuning(7): kern.maxusers controls the scaling of a number of static system tables, including defaults for the maximum number of open files, sizing of net- work memory resources, etc. You can set maxusers to 0 by either recompiling your kernel or by setting the value in loader.conf(5) Ruben Thank you! Gordon Keesler [[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
