Fail to sync after eventual internet connection

Hi, any idea what is going wrong here?

chronyd 4.3.

When booted, the device had no internet connection available. Two
devices are on the same subnet and configured for mutual
synchronisation. This devices recognizes that the system time is off
(by 54 years) but fails to correct it despite "makestep 0.002
40". The other device corrected as expected.

Reference ID : 05A1B894 (5.161.184.148)
Stratum : 3
Ref time (UTC) : Fri Feb 02 14:31:16 2024
System time : 1706820608.000000000 seconds slow of NTP time
Last offset : +0.000893572 seconds
RMS offset : 144616960.000000000 seconds
Frequency : 5.206 ppm fast
Residual freq : +0.092 ppm
Skew : 1.202 ppm
Root delay : 0.041352827 seconds
Root dispersion : 0.001079195 seconds
Update interval : 259.5 seconds
Leap status : Normal
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* 5.161.184.148 2 9 377 135 +2320us[+3214us] +/- 21ms
^- 205.233.73.201 3 7 377 126 +1216us[+1216us] +/- 118ms
^- 74.208.117.38 2 9 377 135 -1224us[-1224us] +/- 71ms
^+ 45.63.54.13 2 9 367 123 +22us[ +22us] +/- 57ms
^x 192.168.64.139 4 6 377 43m +5982us[+6730us] +/- 84ms
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
5.161.184.148 28 14 44m +0.458 1.128 +845us 1344us
205.233.73.201 20 10 23m +0.096 2.333 +1065us 1040us
74.208.117.38 27 18 44m -0.840 1.282 -2107us 1244us
45.63.54.13 27 15 44m -0.768 1.707 -1561us 1469us
192.168.64.139 6 3 20 +67.321 0.764 +183ms 1158ns

Configuration:

# Use the default port for client requests in case it helps installations with picky firewalls
acquisitionport 123

# Where to keep client states across restarts
dumpdir /var/run/chrony

driftfile /var/data/chrony.drift

# Keep the hardware clock in sync
rtcsync

# Just enough to stop flip-flop to isolated network (default 0.001)
stratumweight 0.001

initstepslew 1 0.ntp.service.net 1.ntp.service.net 169.254.8.1

# Step any offset > 2 ms (of the first 40)
makestep 0.002 40

# And slew at no more than 2 ppm to prefer stable frequency
# and reduce impact of short-term inaccurate measurements.
maxslewrate 2

# Prefer stable frequency (smaller frequency error of the system clock)
# over rate of time offset correction (default 3)
corrtimeratio 20

# Expedited Forwarding
dscp 46

pool 1.ntp.service.net iburst trust

allow
cmdallow 169.254.5.230/16
bindcmdaddress 0.0.0.0

# Local fallback clock (default stratum 10)
local orphan
server 169.254.8.1 minpoll 2 maxpoll 6 burst iburst xleave

Log messages from this device:

Jan 1 15:58:25 (none) daemon.info chronyd[510]: Can't synchronise: no selectable sources
Jan 1 15:58:28 (none) daemon.info chronyd[510]: Selected source 192.168.64.139
Jan 1 16:56:20 (none) daemon.info chronyd[510]: Selected source 5.161.184.148 (2.ntp.service.net)
Jan 1 16:56:20 (none) daemon.warn chronyd[510]: System clock wrong by 1706820647.650953 seconds

Log messages from the other device that adjusted time correctly:

Jan 1 16:57:24 (none) daemon.info chronyd[1188]: Selected source 45.33.53.84 (1.ntp.service.net)
Jan 1 16:57:24 (none) daemon.warn chronyd[1188]: System clock wrong by 1706820647.657804 seconds
Feb 2 13:48:12 (none) daemon.warn chronyd[1188]: System clock was stepped by 1706820647.657804 seconds
Feb 2 13:49:18 (none) daemon.info chronyd[1188]: Selected source 129.250.35.251 (1.ntp.service.net)
Feb 2 13:49:18 (none) daemon.warn chronyd[1188]: System clock was stepped by -0.012136 seconds
Feb 2 13:49:45 (none) daemon.info chronyd[1188]: Selected source 192.168.64.181
Feb 2 13:49:45 (none) daemon.warn chronyd[1188]: System clock was stepped by 0.006996 seconds

--
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "help" in the subject.
Trouble? Email [email protected]