New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The file descriptor is unnormal #4375
Comments
@yoster0520 Which process (PID 692) created these pipes? |
|
@yoster0520 What's the complete output of the following command?
|
is
|
@yoster0520 Maybe a too old version of From the manpage of
|
I see the lsof's website, I have the lasted version of lsof. My system is centos 7. Do you have other ways to see the output? I think I can't use the parameter. |
@joschi
Then I use
|
@yoster0520 I think you're mixing up things. In your first post, you wrote that you're using CentOS 6.5. Now you say you're using CentOS 7, but the output you've posted shows that you're using the Graylog omnibus package (e. g. in the OVA or AMI) which only runs on Ubuntu Linux 14.04… |
Production Setup here: uptime 5 Days -> lsof -n -P | grep graylog | wc -l == 3385072 ls /proc/17936/fd/ | wc -l == 2687 open files (17936 == graylog-server process) if the output is needed i can send it via PM to @joschi i have many of these:
|
@gruselglatz Please create a new issue for that and attach the full output as a text file (it doesn't include sensitive information, so this should be safe). You're referring to regular (deleted) files, while @yoster0520 referred to pipes. |
@joschi I also have dozends of pipes... 3.382.385 in particular |
@gruselglatz Then please post the full output of the commands I've previously mentioned in this issue. |
@joschi on CentOS 7 there is only lsof 4.87 so no +E To fulfill your requirements pls give me a equivalent command you would need. |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
I have a production environment that had running three months. Now I found there was more than 4000 file describes on the server node. In my test environment that had running two weeks, there was more than 800 file describes on the server node.
I use
lsof
to check system's file describes. The results as follows:Most of the results are
pipe
. Why?Production Environment
Test Environment
The text was updated successfully, but these errors were encountered: