I have a chrony service (version 3.4-4+deb10u2 - Debian 10) that seems to be running correctly:
chronyc tracking
Reference ID : A29FC801 (time.cloudflare.com)
Stratum : 4
Ref time (UTC) : Mon Sep 12 16:56:00 2022
System time : 0.000000395 seconds fast of NTP time
Last offset : -0.000018043 seconds
RMS offset : 0.000036838 seconds
Frequency : 22.225 ppm fast
Residual freq : -0.002 ppm
Skew : 0.038 ppm
Root delay : 0.033688169 seconds
Root dispersion : 0.054897252 seconds
Update interval : 513.7 seconds
Leap status : Normal
however Linux kernel (4.19.181-1) seems to think otherwise. Systemd command timedatectl appears to be reading the information from org.freedesktop.timedate1 bus
$ timedatectl | grep clock
System clock synchronized: no
is my time really out of sync? How do I convince kernel, that it's synchronized?
$ chronyc sources
210 Number of sources = 4
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* time.cloudflare.com 3 10 377 14h -30us[ -48us] +/- 18ms
^- 38.229.52.9 2 10 377 516 -9566us[-9566us] +/- 122ms
^- ntp24.kashra-server.com 2 10 377 355 -5424us[-5424us] +/- 82ms
^- lax.clearnet.pw 3 10 377 308 -9721us[-9721us] +/- 66ms
/etc/chrony/chrony.conf:
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
server 3.pool.ntp.org iburst
driftfile /var/lib/chrony/drift
rtcsync
makestep 10 3
bindcmdaddress 127.0.0.1
bindcmdaddress ::1
local stratum 10
keyfile /etc/chrony/chrony.keys
noclientlog
logchange 0.5
logdir /var/log/chrony
Workaround: it seems that restarting chrony service will remove the kernel flag.
