-
Titre
VMware scheduled job ran longer than its fixed rate and misfire may be a result of system clock drift -
Description
The following two messages can be observed from the Agent Manager logs:
Collector.esxHardwareCollection scheduled job ran longer [427,995 ms] than its fixed rate of 300,000 ms. 1 scheduled executions were missed.esxHardwareCollection misfired by -128,017 ms and will not be run. Cause of misfire may be a result of system clock drift and correction by a time-sync utility. -
Cause
Collection times out. -
Résolution
SYNCHRONIZATION CHECKS
Check time sync status from vmware tools command line by running:
Windows:C:\Program Files\VMware\VMware Tools>VMwareToolboxCmd.exe timesync status
Also, the following Event Viewer, Event IDs will show ntp synchronization messages:
Event ID 37
Event ID 35
Event ID 47Linux:
vmware-toolbox-cmd timesync status
WORKAROUND 1
Please check and configure the following in VCenter environment:If running on Virtual machines, make sure VMware FGLAMS(Foglight Agent Managers) host, vCenters have correct ntp sync setup with FMS(Foglight Management Server). See more on VMware Timekeeping best practices:WORKAROUND 2
Please increase all these values to the double:Go to Administration │ Agents │ Agent Status
Locate the VMWare Performance Agent in question, then click on Edit Properties.Click Modify the private properties for this agent.1. Please change "Default performance request timeout (sec). Increased as needed" from 120 up to 2402. Scroll down to the very bottom where it says "Data Collection Scheduler" and under "Collector Config" click on Clone, then give it a new name.
Modify the following variables as needed (you may start doubling the values):VMwarePerformance - defaultScheduleCollector Name Default Collection IntervalInventory and Relations 5 minutesPerformance Metrics 5 minutesChange Events Collection 1 minutesHistoric Data Resume Collection 10 minutesNon-VMWare Switch Data Collection 5 minutesNetflow Collection 10 minutesPermissions Collection 0 minutesVFS Collection 15 minutesClick "Save", then click "Save" again, Deactivate and Activate the VMware Agent again.
Please wait for a day to see the changes.
-
Informations supplémentaires
OTHER CHECKS
1. Check your firewall setting to unblock NTP UDP port 123.
2. If running NTP through Windows and if having service "Windows Time" running, please run the following commands from command line to check the status:
w32tm /query /configuration (checks and shows the NTP configuration)
w32tm /query /source (shows the source of the time)
w32tm /query /status (shows the service status, use it to check whether the time is coming from the external NTP servers or the cmos clock)
w32tm /query /status/verbose