Re: NTP fails to sync local clock

[Dan Ritter <dsr@randomstring.org>]

Steve Keller wrote: 
> This is on a Raspberry Pi 3 with Raspberry Pi OS Bookworm 64 Bit,
> ie. Debian 12.  I have uninstalled systemd-timesyncd and installed
> ntpsec, then have commented out the 4 NTP servers
> {0,1,2,3}.debian.pool.ntp.org, and instead added my own server with
> 
>   server -6 my-ntp.my-domain
> 
> When I call ntpdate my-ntp.my-domain manually it steps the time as
> expected.  But then, ntpd doesn't sync the local clock to the NTP
> server, although it seems to consider that server's clock stable:
> 
>   $ ntpq -p
>        remote             refid      st t when poll reach   delay   offset   jitter
>   =================================================================================
>   +my-ntp.my-domain  237.17.204.95    2 u   29   64  377   0.4696  -0.0378   0.0196
>   $ ntpstat 
>   unsynchronised
>      polling server every 1 s
> 
> I usually see a '*' in the first row to indicate that the local clock
> is in sync with that server.  The ntpq(8) man page says about +:
> 
>   +    │ included by the combine algorithm
> 
> In /var/log or with journalctl I don't see any hint what might be the
> reason.  When I let it run, the offset as shown by ntpq grows over
> time.


Does it work without the -6 option?

Does it work if you bring back the pool servers?

-dsr-