So when you execute the command manually (
chronyc tracking) you get
correct data, but with the Checkmk check, you don’t?
It could be, that the chrony cache file isn’t properly updated, but when
you execute the agent manually a few times - as you say - you get the
How exactly are you contacting the “problematic” hosts, meaning: Is their agent output, provided via
xinetd (officially recommended)? Does it make a difference whether you use one method
or the other?
Another idea: As per your initial post, you are on 2.0.0p12. Perhaps you could attempt to update to the latest 2.0.0 version (most recent release is p22: as far as I understand, it might be a “short lived” version) including the agent, and see if this behaviour is mitigated.