Systemd-timesyncd errors since upgrade to 2.4.0p26

Troubleshooting
1

CMK version: 2.4.0p26
OS version: Debian 13

Since the upgrade from 2.4.0p18 to 2.4.0p26 I got frequently warn/crit messages from Systemd Timesyncd check.

It might related to something else (I also updated Debian on the monitored systems) and it happens only on Proxmox VMs not on real hosts.

Since the update, the warn/crit messages are often occur because of Jitter (mostly between 2-4s) or Offset (also between 2-4s).

A sync is done every 1-6h and the deviation is only slightly above the thresholds.

Is there any change implemented in one of the last releases?

Also I haven’t found any option to modify these thresholds in “Service Monitoring Rules” in “Systemd Timesyncd time synchronisation”.

Thanks a lot,

2

Hi @KoMa666 ,

Maybe something changed on your system which caused your timesync values to go above the default thresholds.

By the way, I could not find an option for Jitter, but you can adjust the threshold for offset from the first option “Thresholds for quality of time”.

I would be interested to see a couple of screenshots about the WARN or CRIT alerts for the service.

3

What I can see is that this happens only on Linux VMs in Proxmox with installed Agent.

But not on all, only on some.

Windows VM (with installed Agent) and HW (with installed Agent) do not have these issues.

For example the PVE hosts itself are not having this issue but the VMs running inside having it (all are Debian 13) and it is mostly just a little bit over the threshholds (mostly Jitter of 3s for example or sometimes an offset of 2-3 seconds).