Every day some Agent Managers (FglAMs) running on Virtual Machines (VMs) disconnect, followed by broken agent alarms. The Agent Manager service has not stopped or crashed. Restarting the FglAM seems to temporarily help address the issue.
The FGLAM log on the client host has no entries for the time period. We see only a jump of 7 hours noted in the logs.
Here are some extract from the log that help in figuring out the root cause of the fglam disconnection:
INFO [Upstream Polling-0] com.quest.glue.common.comms.TimeSyncService - Updated the time synchronization with the server from -952 ms to 25,196,044 ms. A change of 25,196,996 ms.
WARN [Upstream Polling-0] com.quest.glue.common.comms.TimeSyncService - This host's clock is out of sync with the server by 25,196,044 ms. This could cause difficulties correlating events logged on the server with local information. It is recommended that you correct the time on this host.
Incorrect time syncing between those servers
Please reference VMware timekeeping best practices on how to setup NTP on those servers.
http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center