The following can be seen within the VMware Agent log file:
YYYY-MM-DD 04:15:59.000 ECHO <VMwarePerformance/5.6.2/VMwarePerformance/agentX-01> WARN [Quartz-533] com.quest.vmware.api.connection.VIService - Connection to the VC cannot be verified. The connection may have been lost.
YYYY-MM-DD 12:15:59.000 ECHO <VMwarePerformance/5.6.2/VMwarePerformance/agentX-01> WARN [Quartz-709] com.quest.vmware.api.connection.VIService - Connection to the VC cannot be verified. The connection may have been lost.
YYYY-MM-DD 16:15:59.000 ECHO <VMwarePerformance/5.6.2/VMwarePerformance/agentX-01> WARN [Quartz-791] com.quest.vmware.api.connection.VIService - Connection to the VC cannot be verified. The connection may have been lost.
No data is missing, so why are the above messages appearing?
The VMware Agent performs a refresh/reset every four hours. Part of this process is to disconnect and then reconnect to the VirtualCenter. As the above shows “connection lost” messages in four hour intervals, this is considered normal behavior and should not result in gaps in data. In addition, random disconnects would also be considered normal as long as the agent reconnects and is able to reconnect fairly quickly. Disconnection only becomes a concern if the agent sustains a state where it is not able to connect.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center