Output of systemd timesyncd jitter is wrong

Troubleshooting
,
1

CMK version:
2.1 CRE
OS version:
Ubuntu 20.04
Error message:
The output of the service Systemd Timesyncd Time seems wrong after the update(Jan 01 1970):

Screenshot 2022-05-31 at 10.48.12
Screenshot 2022-05-31 at 10.48.121610×35 10.3 KB

While this is the output from the agent:

<<<timesyncd>>>
       Server: 192.168.1.11 (192.168.1.11)
Poll interval: 34min 8s (min: 32s; max 34min 8s)
         Leap: normal
      Version: 4
      Stratum: 2
    Reference: 83B06B0D
    Precision: 1us (-29)
Root distance: 7.499ms (max: 5s)
       Offset: +187us
        Delay: 753us
       Jitter: 354us
 Packet count: 293
    Frequency: +6.824ppm

And this from timedatectl:

timedatectl
               Local time: Tue 2022-05-31 08:12:17 UTC
           Universal time: Tue 2022-05-31 08:12:17 UTC
                 RTC time: Tue 2022-05-31 08:12:17
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
2

+1

We have the same problem that because of the jitter the check jumps to WARN/CRIT but we can’t read the discrepancy because of the wrong format.

If it is relevant we are using latest CRE 2.1.0p9 on the VM appliance.

3

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.

5

Hello

i have the same problem with CMK version 2.1.0p22.cre on a host with Debian 10.

The output of the service Systemd Timesyncd Time seems wrong, but timedatectl command is OK.

I have solved the problem with an upgrade of local agent check_mk_agent in latest version 2.2.0p24

best regards
Hugo