-
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
input.vsphere: unable to connect after vCenter reboot #6054
Comments
Some additional info:
|
@prydin What do you think? Possibly an issue with govmomi? |
This looks like an issue with the code that attempts to reauthenticate against vCenter if it loses connectivity. This line
makes me think that it holds onto some reference to an ephemeral object in the old instance of vCenter. I'd have to check the code that handles the reconnection. I'll get back to you once I've done that. |
Yeah... It's a bug in the plugin code. Turns out the connection needs to be torn down one step further to guarantee that no references are reused. We'll try to get this fixed over the next few days. |
Relevant telegraf.conf:
System info:
OS: openSUSE Tumbleweed
Telegraf version: telegraf-1.10.2_linux_amd64
Steps to reproduce:
Expected behavior:
vSphere Plugin reconnects to vCenter and continues metric collection
Actual behavior:
vSphere Plugin tries to reauthenticate with no success until I restart Telegraf
After restarting Telegraf, everything is working normal
Additional info:
This one gets repeatet until Telegraf is restarted
Log:
(stripped down to vc07 as vc01 is still working)
The text was updated successfully, but these errors were encountered: