Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Context deadline exceeded error with Docker plugin #2233
Relevant environment variables
Running on Kubernetes on AWS using the official Telegraf Docker image.
Steps to reproduce:
Just try run Telegraf and configure fetch Kubernetes metrics with the above configuration.
No errors when accessing Kubernetes metrics.
Willing to provide any more information that I might have not provided and is required to debug further.
I've edited the description of the issue (again), provided a better bug report and thereby changed the title to reflect the new discovery.
Initially I thought the issue was the Kubernetes plugin but now can conclude with reasonable confidence that it's the Docker plugin (as seen in the
@sparrc Yes, I did. I set it to 10 seconds and then used with
I hope you don't mind me leaving this open for a little while longer ... so I can change the timeout and leave it running on the cluster (actual deployment as opposed to a
I just saw this same issue today using version 1.2, however I don't have any additional information in terms of stack traces as it apparently tried to access an invalid memory location and segfaulted. This was a random occurrence, so I'm not sure if simply changing the timeout will make a difference.
PS. docker plugin works days ago in this host and still works in other hosts.
have the same with Telegraf 1.8.1 (git: HEAD ae9efb2)
it works for some time and then get sutck.