a follow up to this post:
I still haven't been able to correlate the process and the number of open file descriptors specific to it, however, I have some leads that I am investigating.
in the meantime the following will at least show specifically that the total number of open file descriptors and if this is the true "cause of the issue.
verify the number of open file descriptors on a system : linux tested
cat /proc/sys/fs/file-nr
how do we know how many file descriptors are being used?
[root@pixie proc]# cat /proc/sys/fs/file-nr
3391 969 52427
| | |
| | maximum open file descriptors
| |
| total free allocated file descriptors
total allocated file descriptors
(the number of file descriptors allocated since boot)
excerpt from:
www.netadmintools.com/art295.html
I will follow up this post if I find an answer to the initial question.