On Wed, Oct 23, 2019 at 09:57:49AM +0200, Paul de Weerd wrote:
> Hi all,
>
> While scanning my logs for something unrelated, I came across this
> message from ntpd (note that I have ntpd_flags set to '-v' in
> /etc/rc.conf.local):
>
> 2019-10-21T02:03:50.143Z despair ntpd[57871]: adjusting local clock by
> 5.579152s
>
> I found it weird, because the machine had been up for almost three
> weeks by then - normally, there's some clock adjustment after boot and
> once it's OK, ntpd only adjusts the clock frequency.
>
> I searched all logs and found the following:
>
> # zgrep -he '/bsd: OpenBSD' -e 'ntpd.*adjusting' /var/log/all* | sort | cut
> -f2- -d' ' | sed 's/ by.*//' | uniq -c
> 1 /bsd: OpenBSD 6.4-current (GENERIC.MP) #395: Fri Oct 26 19:59:35 MDT 2018
> 1 ntpd[83741]: adjusting local clock
> 47 ntpd[83741]: adjusting clock frequency
> 1 /bsd: OpenBSD 6.5-beta (GENERIC.MP) #761: Fri Mar 1 21:34:04 MST 2019
> 2 ntpd[79657]: adjusting local clock
> 1 /bsd: OpenBSD 6.5-beta (GENERIC.MP) #761: Fri Mar 1 21:34:04 MST 2019
> 1 ntpd[30514]: adjusting local clock
> 16 ntpd[30514]: adjusting clock frequency
> 1 /bsd: OpenBSD 6.5-beta (GENERIC.MP) #761: Fri Mar 1 21:34:04 MST 2019
> 2 ntpd[38581]: adjusting local clock
> 5 ntpd[38581]: adjusting clock frequency
> 1 /bsd: OpenBSD 6.5 (GENERIC.MP) #847: Tue Apr 9 09:12:46 MDT 2019
> 1 ntpd[94340]: adjusting local clock
> 30 ntpd[94340]: adjusting clock frequency
> 1 /bsd: OpenBSD 6.5-current (GENERIC.MP) #6: Tue Jun 4 15:05:10 MDT 2019
> 1 ntpd[4423]: adjusting local clock
> 66 ntpd[4423]: adjusting clock frequency
> 1 /bsd: OpenBSD 6.5-current (GENERIC.MP) #6: Tue Jun 4 15:05:10 MDT 2019
> 1 ntpd[94384]: adjusting local clock
> 16 ntpd[94384]: adjusting clock frequency
> 1 /bsd: OpenBSD 6.5-current (GENERIC.MP) #6: Tue Jun 4 15:05:10 MDT 2019
> 1 ntpd[43359]: adjusting local clock
> 5 ntpd[43359]: adjusting clock frequency
> 1 /bsd: OpenBSD 6.6-beta (GENERIC.MP) #335: Sun Sep 29 21:47:20 MDT 2019
> 1 ntpd[57871]: adjusting local clock
> 2 ntpd[57871]: adjusting clock frequency
> 1 ntpd[57871]: adjusting local clock
> 1 ntpd[57871]: adjusting clock frequency
> 4 ntpd[57871]: adjusting local clock
> 2 ntpd[57871]: adjusting clock frequency
> 1 ntpd[57871]: adjusting local clock
> 1 ntpd[57871]: adjusting clock frequency
> 4 ntpd[57871]: adjusting local clock
> 2 ntpd[57871]: adjusting clock frequency
> 1 ntpd[57871]: adjusting local clock
> 1 ntpd[57871]: adjusting clock frequency
> 11 ntpd[57871]: adjusting local clock
> 2 ntpd[57871]: adjusting clock frequency
> 1 ntpd[57871]: adjusting local clock
> 1 ntpd[57871]: adjusting clock frequency
> 4 ntpd[57871]: adjusting local clock
> 1 ntpd[57871]: adjusting clock frequency
>
> (here things alternate between adjusting clock and adjusting frequency
> 40 times in 22 days).
>
> So from 6.4-current, back in October 2018, there was indeed one or two
> 'adjusting local clock' after boot, followed by a bunch of 'adjusting
> clock frequency'. However, since the update to 6.6-beta end of
> September, ntpd is regularly adjusting the local clock.
>
> Is anyone else seeing this? Could it be a sign of broken hardware or
> is the battery of my RTC dead?
>
> Thanks,
>
> Paul
>
> --
> >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
> +++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
> http://www.weirdnet.nl/
>
I could * this has to do with the logging changes. Previously, debug
messages could disappear because of wrong logging setup. In non -v
mode, only big adjustments are logged. Sadly you stripped those
numbers away so i cannot tell how big the adjustments are.
-Otto
