-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
inputs.processes fails with "no such process" #2815
Comments
noidi
pushed a commit
to noidi/telegraf
that referenced
this issue
May 16, 2017
2 tasks
danielnelson
pushed a commit
that referenced
this issue
May 17, 2017
danielnelson
added a commit
that referenced
this issue
May 17, 2017
danielnelson
added a commit
that referenced
this issue
May 19, 2017
vlamug
pushed a commit
to vlamug/telegraf
that referenced
this issue
May 30, 2017
vlamug
pushed a commit
to vlamug/telegraf
that referenced
this issue
May 30, 2017
jeichorn
pushed a commit
to jeichorn/telegraf
that referenced
this issue
Jul 24, 2017
jeichorn
pushed a commit
to jeichorn/telegraf
that referenced
this issue
Jul 24, 2017
maxunt
pushed a commit
that referenced
this issue
Jun 26, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Our Telegraf installations occasionally produce error messages like the following:
The error is triggered when a process is terminated while
readProcFile
(plugins/inputs/system/processes.go
) is reading the process's/proc/<pid>/stat
file.System info:
All versions including the current master.
Steps to reproduce:
The bug is triggered by a race condition so it's quite hard to reproduce in Telegraf (we get 10-20 errors per day from 500+ hosts), but here's a little test program that uses a copy of
readProcFile
to demonstrate the issue.Running the test program multiple times tends to cause at least one failure:
Expected behavior:
Telegraf already checks for process termination between listing the
/proc/*/stat
files and reading them. Process termination betweenopen()
andread()
should be handled the same way (i.e. without errors).Actual behavior:
The text was updated successfully, but these errors were encountered: