You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see in the above output, lsb_release had been running for quite some time, which seemed suspicious. So I killed it, and once I did, the box began reporting again. However, since it was stuck on lsb_release, none of the other measurements had been happening, so I had actually lost 20 minutes worth of data (as opposed to it getting buffered somewhere).
I'm not entirely sure why telegraf was calling lsb_release (I certainly don't explicitly do it anywhere), and am curious if there is someway to put a timeout on it.
I noticed that one of my telegraf nodes (0.13.0 on Debian Wheezy amd64) stopped reporting for almost 20 minutes.
As you can see in the above output,
lsb_release
had been running for quite some time, which seemed suspicious. So I killed it, and once I did, the box began reporting again. However, since it was stuck onlsb_release
, none of the other measurements had been happening, so I had actually lost 20 minutes worth of data (as opposed to it getting buffered somewhere).I'm not entirely sure why telegraf was calling
lsb_release
(I certainly don't explicitly do it anywhere), and am curious if there is someway to put a timeout on it.Here's my config:
The text was updated successfully, but these errors were encountered: