Environment:
Raspberry pi 3 running chrony server
gps data + PPS connected to headers
Error:
System clock wrong by 3302.382879 seconds
This Raspberry pi 3 is only used as a chrony ntp time server for the homelab LAN and works great except while booting after a power failure. This other thread Newbie questions regarding Chrony reports the same error and it's considered normal since it gets corrected later.
The problem is there is a about a two minute window where chrony is providing incorrect time after booting from a power failure and all the LAN clients are also booting after a power failure and getting this bad time. Is there a way to tell chrony to delay distributing time to clients until the clock was stepped to the correct time?
Chrony logs with error of 3302 seconds when clock gets set from online.
Chrony logs with error of 2424 seconds when clock gets set from the GPS fix.
My router only gets ntp time every hour so has a 3302 sec error for an hour. Yes a hardware RTC would probably fix this but there must be a software fix.
Raspberry pi 3 running chrony server
gps data + PPS connected to headers
Error:
System clock wrong by 3302.382879 seconds
This Raspberry pi 3 is only used as a chrony ntp time server for the homelab LAN and works great except while booting after a power failure. This other thread Newbie questions regarding Chrony reports the same error and it's considered normal since it gets corrected later.
The problem is there is a about a two minute window where chrony is providing incorrect time after booting from a power failure and all the LAN clients are also booting after a power failure and getting this bad time. Is there a way to tell chrony to delay distributing time to clients until the clock was stepped to the correct time?
Chrony logs with error of 3302 seconds when clock gets set from online.
Code:
-- Boot e6aaac0513c84dbcb3eb18753fcc359e --Nov 04 13:17:08 raspberrypi3 systemd[1]: Starting chrony.service - chrony, an NTP client/server...Nov 04 13:17:08 raspberrypi3 chronyd[607]: chronyd version 4.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +AS>Nov 04 13:17:08 raspberrypi3 chronyd[607]: Frequency -1.827 +/- 0.001 ppm read from /var/lib/chrony/chrony.driftNov 04 13:17:08 raspberrypi3 chronyd[607]: Using right/UTC timezone to obtain leap second dataNov 04 13:17:08 raspberrypi3 chronyd[607]: Loaded seccomp filter (level 1)Nov 04 13:17:08 raspberrypi3 systemd[1]: Started chrony.service - chrony, an NTP client/server.Nov 04 13:18:56 raspberrypi3 chronyd[607]: Selected source 158.69.247.84 (2.debian.pool.ntp.org)Nov 04 13:18:56 raspberrypi3 chronyd[607]: System clock wrong by 3302.382879 secondsNov 04 14:13:58 raspberrypi3 chronyd[607]: System clock was stepped by 3302.382879 secondsNov 04 14:13:58 raspberrypi3 chronyd[607]: System clock TAI offset set to 37 secondsNov 04 14:14:18 raspberrypi3 chronyd[607]: Selected source PPSNov 04 14:17:14 raspberrypi3 chronyd[607]: Source 198.50.127.72 replaced with 216.232.132.95 (2.debian.pool.ntp.org)Code:
-- Boot 69b4f0fab3cc4c92bcc0a1025d8c3914 --Nov 04 23:17:08 raspberrypi3 systemd[1]: Starting chrony.service - chrony, an NTP client/server...Nov 04 23:17:09 raspberrypi3 chronyd[610]: chronyd version 4.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +AS>Nov 04 23:17:09 raspberrypi3 chronyd[610]: Frequency -1.747 +/- 0.044 ppm read from /var/lib/chrony/chrony.driftNov 04 23:17:09 raspberrypi3 chronyd[610]: Using right/UTC timezone to obtain leap second dataNov 04 23:17:09 raspberrypi3 chronyd[610]: Loaded seccomp filter (level 1)Nov 04 23:17:09 raspberrypi3 systemd[1]: Started chrony.service - chrony, an NTP client/server.Nov 04 23:19:16 raspberrypi3 chronyd[610]: Selected source NMEANov 04 23:19:16 raspberrypi3 chronyd[610]: System clock wrong by 2424.217961 secondsNov 04 23:59:40 raspberrypi3 chronyd[610]: System clock was stepped by 2424.217961 secondsNov 04 23:59:40 raspberrypi3 chronyd[610]: System clock TAI offset set to 37 secondsNov 04 23:59:40 raspberrypi3 chronyd[610]: Selected source PPSStatistics: Posted by yoyoma2 — Wed Nov 05, 2025 6:31 am — Replies 0 — Views 4