-
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
docker plugin crash #1195
Comments
@babaev, which version of telegraf? |
@zstyblik , |
I have the same issue running telegraf 0.13. Inputs like: system, CPU, MEM, DISK, DISKIO are working fine, but docker input plugin fails with |
I know a fix for this, but the workaround would be to extend the timeout of your docker plugin. Currently it defaults to 5s but you can set it higher. just do:
|
Let me make it clear. The problem is not that docker doesn`t respond - it may happen due to many reasons. My concern is that if it happens telegraf crashes. And it happens because here:
Modifying the check
To something like
Should make it work correctly. |
@babaev correct. |
Please include this fix in the next point release. |
it will be in 0.13.1 |
Just hit this one. @sparrc , when does 13.1 come out? |
If docker becomes unresponsive to requests docker plugin panics and crashes telegraf.
My case:
The reason seems to be in plugins/inputs/docker/docker.go:226
Since r might be nil if err != nil shouldn`t it just return err instead of printing it?
The text was updated successfully, but these errors were encountered: