-
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
Context deadline exceeded error with Docker plugin #2233
Comments
(edited description) |
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 Which now leads me to issue #1195 ... seems I'm having the same problem (yet there was a fix added by @sparrc that was/should have been merged in in |
this is unrelated to #1195, did you try increasing 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'm going to close this for lack of updates, if you have any more details and still think it's an issue please feel free to open a new one |
Sure. Sorry about that ... forgot to report back. I changed timeout to 10s but issue persisted. Opted to leave out Docker input and Kubernetes plugin gave me much of what I needed. |
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. |
Same here.
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 ae9efb2f)
plugin config:
it works for some time and then get sutck. |
same here, some news?? |
I believe this error indicates a timeout talking to the docker api, can you try setting the timeout higher? You may be overloading the docker engine, it also might help to increase the interval or limit the containers that are matching. |
As a fix let's change the log message to better indicate a timeout. |
Bug report
Relevant
telegraf.conf
Relevant environment variables
System info:
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.
Expected behavior:
No errors when accessing Kubernetes metrics.
Actual behavior:
Additional info:
Willing to provide any more information that I might have not provided and is required to debug further.
The text was updated successfully, but these errors were encountered: