"Cause of misfire may be a result of system clock drift" errors in FglAM log (4308480)

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

"Cause of misfire may be a result of system clock drift" errors in FglAM log
Description

Clock drift warnings like the following appear in the FglAM log.
WARN The <FglAM Unique ID>/HostAgents/5.8.5/WindowsAgent/Monitor@<Remote-Hostname>-Collector.collect scheduled job ran longer [371,270 ms] than its fixed rate of 90,000 ms. 4 scheduled executions were missed.
WARN Scheduled job <FglAM Unique ID>/HostAgents/5.8.5/WindowsAgent/Monitor@<Remote-Hostname>-Collector.collect misfired by -281,274 ms and will not be run. Cause of misfire may be a result of system clock drift and correction by a time-sync utility.
Resolution
RESOLUTION 1
Test the hosts internal clock stability to verify that whether or not the error messages are legitimate. Enable the Windows Time Service debug logging to get further details.
VMs are susceptible to clock drift and jitter. Enable the logging by following the steps described here.
RESOLUTION 2
1. On the Foglight Agent Manager, go to <FglAM home>/state/default/config/fglam.config.xml
2. Edit the file
3. Find the following line
  <config:upstream-verified max-queue-size="-1" max-disk-space="512" max-batch-size="250" allow-runtime-change="true"/>
4. Change max-disk-space="512" to max-disk-space="4096"
5. Save fglam.config.xml

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title