4 ms·
What was the exact error? What kind of files were open? If you want to share, I'm sure lots of us would be interested to hear the details so we know what to loo
by shafqat 18y ago
What was the exact error? What kind of files were open? If you want to share, I'm sure lots of us would be interested to hear the details so we know what to look out for.
- jey 18y agoSounds like the limit for the maximum number of open File Descriptors (FDs) was reached. On Linux, you can check the limit by doing: cat /proc/sys/fs/file-max You can change this limit: echo 100000 > /proc/sys/fs/file-max This limit is also available through the "fs.file-max" sysctl. The "lsof" tool is great for seeing what FDs a process has open. Note that FDs are used for more than just regular files: directories, sockets, pipes, and other file-like objects too.
- abstractbill 18y agonetstat is also handy here (e.g. sometimes you find a single remote IP is holding open way more sockets than it should be).
- axod 18y agoAlso ulimit and /etc/security/limits.conf The default for max open files (1024) is ridiculously low. First thing to do when installing linux, up the max open file limits.
- pg 18y agoIt looks as if most of the file descriptors in use at any given time refer to closed tcp connections. We're still trying to figure out what this means.