-
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
vsphere Client.Timeout exceeded while awaiting headers #5133
Comments
Add |
@prydin Can you help me understand this recommendation better, isn't the default already timeout 60s in 1.9.0? |
I sas assuming this was 1.8.x, but maybe not. |
Yes, I run telegraf 1.9: I set the value 60 but the timeouts keep coming. Actually I putted it to 120s and nothing changed. A pity that debug mode does not show what is doing when timeouts occur or the SeverFaultCode. |
Try this with version 1.10 of telegraf. There's been some improvement of the timeout handling. |
tried with 1.10.3 and timeout = "1800s" ... the messages are still comming ... |
There has been a lot of changes to the vsphere plugin since this bug report was opened, is this still an issue with the latest version of Telegraf? If it is please post config and logs and we can investigate this problem. |
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you! |
Relevant telegraf.conf:
file telegraf.d/manu010.vm.conf
file telegraf.d/manu001.vm.conf
Inmediately after telegraf stars manu100.vm outputs this error:
No metrics is stored in influxdb for manu010.vm.
From time to time appears errors for the other vcenter, manu001.vm:
There is metrics for manu001 but not continually. Fails for an hour and after that continues getting metrics again.
The text was updated successfully, but these errors were encountered: