-
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
system plugin crash telegraf (1.2.0/1.2.1) #2356
Comments
that's strange, can you provide the output of |
BTW you should be able to workaround this by setting |
|
it seems like this could only panic if /proc/stat was empty: https://github.com/shirou/gopsutil/blob/master/cpu/cpu_linux.go#L39 so I'm not sure how this is happening, but the fix should be simple enough. |
does the host have the |
since it's lxc container I can somehow imagine lack of |
don't really know why this would be the case, but I suppose there are always edge-cases. see influxdata/telegraf#2356
closes influxdata#2356
closes influxdata#2356
Directions
Looks like telegraf crash pretty frequently when collects system metrics.
Relevant telegraf.conf:
System info:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
LXC container
Steps to reproduce:
In our case we start telegraf and few minutes later we have crash.
Expected behavior:
Agent doesn't crash
Actual behavior:
Agent crashes
Additional info:
Telegraf 1.2.1:
Telegraf 1.2.0:
The text was updated successfully, but these errors were encountered: