In one of our APM capture groups, the Archiver (or Sniffer) appliance is giving an error because the clock skew is 25 seconds off while the other capture group's Appliances are showing the clock skew being within 2 minutes as ‘OK’. So which is it? How close do the clocks need to be? Is it ok to be 1 minute out of sync, for example?
This is just misleading text for the "ok" status. You're actually fine, since you have the "ok" status
This small text defect is being tracked as APMDATA-1938: "Clock sync "okay" message in Capture Group 'Test' should match up with error/warning messages"
When performing a "Capture Group Test" a warning or error is indicated if an appliance remote to the appliance with foglight's clock varies more than 15 or 25 seconds respectively. These actual values had been changed but we forgot to change the "okay" message to match.
When clocks are "ok", the message should read something like:
The Sniffer xxx at yyy system clock is within 15 seconds of this Foglight's clock.
The Sniffer xxx at yyy system clock is within two minutes of this Foglight's clock.
This message is safe to ignore.This is just misleading text for the "ok" status. You're actually fine, since you have the "ok" status
Fixed in APM 5.9.7, patch 22.214.171.124.
APMDATA-1938 Fixed issue where the system clock messages in Capture Group "Test" were misleading.