This first appeared after a routine update in F35 (I didn’t notice at first so I don’t what was updated that caused the problems), but it persisted into F36. The issue is that my clock is consistently wrong, and only restarting chronyd corrects the time.
To complicate matters I use a personal VPN. This is important because the clock is often about an hour out, my timezone is BST (UTC+1) whilst my VPN usually makes me appear in CET (UTC+2). Because of this, I set ‘Automatic Time Zone’ off, but I don’t think that time difference is a coincidence.
$ journalctl -r -u chronyd
May 13 19:48:00 cams-laptop chronyd[152370]: Selected source 2606:4700:f1::123 (2.fedora.pool.ntp.org)
May 13 19:46:48 cams-laptop chronyd[152370]: Selected source 185.125.24.59 (2.fedora.pool.ntp.org)
May 13 19:45:49 cams-laptop chronyd[152370]: Selected source 2606:4700:f1::123 (2.fedora.pool.ntp.org)
May 13 19:45:44 cams-laptop chronyd[152370]: Source 2001:4168:3::2 online
May 13 19:45:44 cams-laptop chronyd[152370]: Source 2606:4700:f1::123 online
May 13 19:45:44 cams-laptop chronyd[152370]: Source 2001:4168:1::1 online
May 13 19:45:41 cams-laptop chronyd[152370]: System clock wrong by -3599.347369 seconds
May 13 19:45:41 cams-laptop chronyd[152370]: Selected source 185.125.24.59 (2.fedora.pool.ntp.org)
May 13 19:45:36 cams-laptop chronyd[152370]: Source 185.125.24.59 online
May 13 19:45:36 cams-laptop chronyd[152370]: Can't synchronise: no selectable sources
May 13 19:45:36 cams-laptop chronyd[152370]: Forward time jump detected!
May 13 18:28:14 cams-laptop chronyd[152370]: Source 185.125.24.59 offline
May 13 18:28:13 cams-laptop chronyd[152370]: Source 2606:4700:f1::123 offline
May 13 18:28:13 cams-laptop chronyd[152370]: Source 2001:4168:3::2 offline
May 13 18:28:13 cams-laptop chronyd[152370]: Source 2001:4168:1::1 offline
May 13 12:01:01 cams-laptop chronyd[152370]: Selected source 2606:4700:f1::123 (2.fedora.pool.ntp.org)
May 13 11:40:27 cams-laptop chronyd[152370]: Selected source 2001:4168:1::1 (2.fedora.pool.ntp.org)
May 13 11:39:25 cams-laptop chronyd[152370]: Source 217.147.208.1 replaced with 2606:4700:f1::123 (2.fedora.pool.ntp.org)
May 13 11:39:23 cams-laptop chronyd[152370]: System clock TAI offset set to 37 seconds
May 13 11:39:23 cams-laptop chronyd[152370]: System clock was stepped by -2740.021035 seconds
May 13 12:25:03 cams-laptop chronyd[152370]: System clock wrong by -2740.021035 seconds
May 13 12:25:03 cams-laptop chronyd[152370]: Selected source 2001:4168:3::2 (2.fedora.pool.ntp.org)
May 13 12:24:56 cams-laptop systemd[1]: Started chronyd.service - NTP client/server.
May 13 12:24:56 cams-laptop chronyd[152370]: Loaded seccomp filter (level 2)
May 13 12:24:56 cams-laptop chronyd[152370]: Using right/UTC timezone to obtain leap second data
May 13 12:24:56 cams-laptop chronyd[152370]: Frequency -5.160 +/- 0.102 ppm read from /var/lib/chrony/drift
May 13 12:24:56 cams-laptop chronyd[152370]: chronyd version 4.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG)
May 13 12:24:56 cams-laptop systemd[1]: Starting chronyd.service - NTP client/server...
This log shows a typical cycle from chrony in journald. You can see:
- At 12:24:56 the service starts by me hitting the ‘Automatic Time Zone’ checkbox in Settings. It syncs with the NTP servers and realises that it’s ~45 mins fast, and so sets the clock back (
System clock was stepped by -2740.021035 seconds) - Sometime later a bunch of NTP servers drop offline and sometime after that chronyd realises that the time is wrong (
System clock wrong by -3599.347369 seconds) but then it doesn’t adjust it!
Any ideas how to fix this?