Red Hat Bugzilla – Bug 66525
too many files open in system
Last modified: 2008-08-01 12:22:52 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)
Description of problem:
2.4.9-31enterprise running on Compaq DL360 2 cpu will hang after several days.
Any command you attempt displays error "too many open files in system"
We are logging file-nr every 5 minutes and notice the number of allocated
filehandles gradually increase until hits 8192, the system then hangs soon
Have looked over bug #40071 that is similar but not quite the same. This
behavior is not happening on the test server we have running 2.4.9-31 (not
enterprise) on a Compaq DL360 with one cpu. Both servers are running the same
application, albeit under different loads.
Attached is the filehandle log and lsof, ps and top output.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.start up server
3.watch allocated filehandles rise until system hangs
Actual Results: too many files open in system
Expected Results: file handle allocation should not grow. This is what we see
on the test server.
Created attachment 60568 [details]
log of /proc/sys/fs/file-nr every 5 minutes
Created attachment 60569 [details]
lsof ps -elf and top just before server hang
Created attachment 60570 [details]
output log of wc on open files, taken after server had been rebooted
Created attachment 60571 [details]
ps output to match fd_list after server rebooted
Have rebooted server to use 2.4.9-31 in single cpu mode, not enterprise or smp
version of kernel. Steady increase in filehandle allocations continues. Value
of file-max increased from 8192 to 32768.
At this point we are working with the java developers to see how we can better
isolate the problem.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/