Skip to content
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

Closed
babaev opened this issue May 13, 2016 · 9 comments
Closed

docker plugin crash #1195

babaev opened this issue May 13, 2016 · 9 comments

Comments

@babaev
Copy link

babaev commented May 13, 2016

If docker becomes unresponsive to requests docker plugin panics and crashes telegraf.

My case:

  • Running telegraf in docker container
  • Querying docker via docker.sock, provided via docker volume
  • At some point due to heavy load/unknown reasons connection to docker fails with "context deadline exceeded". (Full message from telegraf in logs: "Error getting docker stats: An error occurred trying to connect: context deadline exceeded")
  • telegraf crashes with panic:
goroutine 4571798 [running]:
panic(0x1072740, 0xc820012070)
    /usr/local/go/src/runtime/panic.go:464 +0x3e6
github.com/influxdata/telegraf/plugins/inputs/docker.(*Docker).gatherContainer(0xc8207c4200, 0xc820654b40, 0x40, 0xc820654b80, 0x1, 0x4, 0xc82059ce10, 0x47, 0xc82059ce60, 0x47, ...)
    /home/user/go/src/github.com/influxdata/telegraf/plugins/inputs/docker/docker.go:226 +0xa8c
github.com/influxdata/telegraf/plugins/inputs/docker.(*Docker).Gather.func1(0xc820519f80, 0xc8207c4200, 0x7ff06e6fbc00, 0xc82072d3c0, 0xc820654b40, 0x40, 0xc820654b80, 0x1, 0x4, 0xc82059ce10, ...)
    /home/user/go/src/github.com/influxdata/telegraf/plugins/inputs/docker/docker.go:117 +0xa6
created by github.com/influxdata/telegraf/plugins/inputs/docker.(*Docker).Gather
    /home/user/go/src/github.com/influxdata/telegraf/plugins/inputs/docker/docker.go:122 +0x5fb

The reason seems to be in plugins/inputs/docker/docker.go:226

r, err := d.client.ContainerStats(ctx, container.ID, false)
if err != nil {
    log.Printf("Error getting docker stats: %s\n", err.Error())
}
defer r.Close()

Since r might be nil if err != nil shouldn`t it just return err instead of printing it?

@zstyblik
Copy link
Contributor

@babaev, which version of telegraf?

@babaev
Copy link
Author

babaev commented May 13, 2016

@zstyblik , 0.12.1-83-g40dccf5 but the code I mention is still in master

@sporokh
Copy link

sporokh commented May 13, 2016

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 context deadline exceeded

@sparrc
Copy link
Contributor

sparrc commented May 13, 2016

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:

[[inputs.docker]]
  ...
  timeout = "10s"

@babaev
Copy link
Author

babaev commented May 13, 2016

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:

https://github.com/influxdata/telegraf/blob/master/plugins/inputs/docker/docker.go#L226

r might be nil in which case it is nil pointer dereference panic.

Modifying the check

if err != nil {
        log.Printf("Error getting docker stats: %s\n", err.Error())
    }

To something like

if err != nil {
        return fmt.Errorf("Error getting docker stats: %s\n", err.Error())
    }

Should make it work correctly.

@zstyblik
Copy link
Contributor

@babaev correct.

zstyblik added a commit to zstyblik/telegraf that referenced this issue May 15, 2016
Commit fixes crash in Docker input plugin caused by the fact that return value
might be nil when error occurs.
zstyblik added a commit to zstyblik/telegraf that referenced this issue May 15, 2016
Commit fixes crash in Docker input plugin caused by the fact that return value
might be nil when error occurs.
@sparrc sparrc closed this as completed in 39df263 May 18, 2016
@dvenza
Copy link

dvenza commented May 18, 2016

Please include this fix in the next point release.

@sparrc
Copy link
Contributor

sparrc commented May 18, 2016

it will be in 0.13.1

@jvalencia
Copy link

Just hit this one. @sparrc , when does 13.1 come out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants