-
Notifications
You must be signed in to change notification settings - Fork 49
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
data getter for processes shouldn't assume that every uid has pwd entry #24
Comments
I'm seeing this as well. Debating what to replace it with. |
Oh my! 10 minutes with longview running:
This is crazy! And yes I have many containers running. |
Same problem here. |
Same here. Tons of warnings with docker containers. |
As it turns out, the fix is actually really simple. |
I've spent the last 3 months raising ticket after ticket with linode support about this, and they keep suggesting random things like "try uninstalling and then reinstalling the agent" and seem completely unaware of this issue that has been open for years. |
@jamezpolley I've actually contacted them directly suggesting they pay attention to this repo as there are several outstanding pull requests. They didn't seem too interested at all. Kind of sad really. If you clone my fork, and use it instead you won't have to deal with this issue anymore. |
Thanks @willvincent Since applying this change, data in the longview console is updating pretty much live for the first time ever. |
Investigating high disk usage on a box that's been running for a few years. 17GB of this error message. Ugh.
|
Processes can run (e.g. inside docker containers) with user ids that don't have valid pwd entries on the host system. The code at
longview/Linode/Longview/DataGetter/Processes.pm
Line 68 in 240db8f
$proc{user}
is later used inlongview/Linode/Longview/DataGetter/Processes.pm
Lines 101 to 108 in 240db8f
The text was updated successfully, but these errors were encountered: