-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Thousands of /tmp/pluginXXXX files #2844
Comments
@carlpett Have these clients always been running 0.5.6 or they have been upgraded from older versions? Also have they been restarted a lot? |
They've been upgraded: 0.4.0->0.4.1->0.5.0->0.5.4->0.5.5->0.5.6. First install was a bit over a year ago. |
@carlpett I didn't notice the timestamps when I first looked at the issue. Are the vast majority of the plugins files recent? There was a bug that was fixed in an older version that meant we weren't cleaning up the files, that is why I asked if the node has been upgraded. |
@dadgar Yep, almost all of them are from the last week or so. |
@carlpett I wonder if you just had a non-clean shutdown of Nomad that didn't let it clean itself up? |
@carlpett Ignore my questions, I verified that this is happening! Will hopefully get a fix in 0.6.1 |
This PR fixes a leaking of the unix socket used when launching a syslog server for the Docker driver. Fixes #2844
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.5.6
Operating system and Environment details
Centos 7.2
Issue
We just noticed we have thousands of zero-byte files named like /tmp/plugin000227203 on some of our nomad clients.
Reproduction steps
Unclear.
Nomad Client logs (if appropriate)
Looking at some files' time-stamps:
# ls -l plugin* --sort=time --time-style=full-iso | head srwxr-xr-x. 1 nomad nomad 0 2017-07-14 18:58:03.584312115 +0200 plugin913505122 srwxr-xr-x. 1 nomad nomad 0 2017-07-14 18:58:03.571312377 +0200 plugin804998223
Here are nomad and docker logs from this time:
I'm not sure what a terminal alloc is? Possibly it is unrelated to the files, and those correspond to container creation?
The text was updated successfully, but these errors were encountered: