Dear list,
In my pound logs I have been getting messages like this:
--start--
Oct 16 19:37:04 hsc18 pound: backend xx.xx.xx.46:80 create: Too many open
files
Oct 16 19:37:04 hsc18 pound: HTTP accept: Too many open files
Oct 16 19:37:04 hsc18 pound: backend xx.xx.xx.45:80 create: Too many open
files
Oct 16 19:37:04 hsc18 pound: backend xx.xx.xx.44:80 create: Too many open
files
Oct 16 19:37:04 hsc18 pound: HTTP accept: Too many open files
Oct 16 19:37:04 hsc18 pound: backend xx.xx.xx.52:80 create: Too many open
files
--done--

Which according to my googling is caused by a lack of available file
descriptors but on this linux 2.4 box checking the contents of the 2nd
field of the file /proc/sys/fs/file-nr which shows available fds here is
the result:

[snip]
  159 open Mon Oct 16 19:37:00 EDT 2006
  168 open Mon Oct 16 19:37:01 EDT 2006
  164 open Mon Oct 16 19:37:02 EDT 2006
  168 open Mon Oct 16 19:37:03 EDT 2006
  182 open Mon Oct 16 19:37:05 EDT 2006
[snip]

(for the missing second the results were over 200 fds as per my logging script
rules)

The logs never show fds dropping to 0, and the issues with too
many open files going on for a couple minute stretches every once in a
while. The only reason I detected these at all were I was sitting there
and my nagios alarms went off and then I tried connecting to my  
website and got a 503 error.

We are still running pound 1.9 here, they have been running fine for a  
long time, this is now happening on 2 machines with identical installs.

Any ideas what could be going on here?


brian
--
Never be afraid to tell the world who you are.
              -- Anonymous

On Tue, 2006-10-17 at 09:55 -0400, gauze(at)dropdead.org wrote:[...]

The fact that the system has available fds does NOT imply Pound having
them. You need to look at the exact ulimits defined for the user which
starts Pound, in the start-up script.[...]