Help troubleshooting VP210 / Event 96/89 Events

[khitsgmbh]

Hello,

since one week we get constant errors on one of our 4 collectors:

VP210 Datacomm connection lost to VC target xxxx. The VMware API error returned was 'Thread was being aborted.'. No performance data will be obtained from this source until connection can be restored.

and

VP050 Error encountered retrieving performance metrics for a cluster on xxx. The VMware API error returned was 'Thread was being aborted.'.

These errors occur every few hours.
All other collector work fine (use same VC, same network, sam user) and there are no errors in the VC logs itself.
Do you have any hints/advice how to find the root cause and fix the issue?

Best regards,
Dirk

[Alec King]

Hi Dirk,

That error can be tricky to troubleshoot - there could be various causes.
What's the monitoring load on this Collector, compared to the other three? These errors can be caused when the Collector is stressed, using high cpu/memory.
Alternatively, the problem can be on the vCenter side - some configuration or permissions error specific to the Clusters/Hosts that this Collector monitors.

I'd advise you open a case with our excellent support team - they will help you get to the root cause of this error.

Cheers,
Alec

[khitsgmbh]

Hi Alec,

the collector has an average CPU usage of under 20% and at any point in time 2GB free RAM. Monitoring Load ist below 25%...

I will open up a support case by tomorrow.

Thanks,
Dirk

[Alec King]

Thanks Dirk - in that case, I suspect one 'bad' host in a Cluser is causing our API query to fail. Support can dig into your logfiles and prove the cause.

Thanks!
Alec