Re: time changed from 2020-07-03 to 2022-05-18

2020-07-03 Thread ASSI via devel
Udo van den Heuvel via devel writes: > Garmin gps18x on the serial port with USB power. > With just $GPGGA and $GPRMC enabled, so where did it find that weird date? If you had the clockstats file enabled, you would be able to see what message ntpd received at that point. Since you have RMC enable

Re: time changed from 2020-07-03 to 2022-05-18

2020-07-03 Thread James Browning via devel
On Fri, Jul 3, 2020, at 6:05 AM Udo van den Heuvel via devel wrote: > > On 03-07-2020 15:00, Hal Murray wrote: > >> How can I avoid this from happening again? > > > > That isn't enough info to figure out what happened. Somehow, ntpd thought > > the > > time was way off, and you had the -g switch

Re: time changed from 2020-07-03 to 2022-05-18

2020-07-03 Thread Udo van den Heuvel via devel
On 03-07-2020 15:00, Hal Murray wrote: >> How can I avoid this from happening again? > > That isn't enough info to figure out what happened. Somehow, ntpd thought > the > time was way off, and you had the -g switch on that allowed it to take big > jumps. If you turn off the -g switch, ntpd w

Re: time changed from 2020-07-03 to 2022-05-18

2020-07-03 Thread Hal Murray via devel
> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time stepped by 59097600.478559 > May 18 10:06:48 boombox ntpd[2055]: CLOCK: time changed from 2020-07-03 to > 2022-05-18 > We're running a fairly recent git version of ntpsec: ntpsec-1.1.9-0.fc31.x86_6 > 4 on Fedora 31 on kernel.org 5.7.7. > How ca

Re: time changed from 2020-07-03 to 2022-05-18

2020-07-03 Thread Udo van den Heuvel via devel
On 03-07-2020 10:34, ASSI via devel wrote: > Udo van den Heuvel via devel writes: >> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time stepped by 59097600.478559 >> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time changed from 2020-07-03 to >> 2022-05-18 > > That's why you don't trust the GPS time u

Re: time changed from 2020-07-03 to 2022-05-18

2020-07-03 Thread ASSI via devel
Udo van den Heuvel via devel writes: > May 18 10:06:48 boombox ntpd[2055]: CLOCK: time stepped by 59097600.478559 > May 18 10:06:48 boombox ntpd[2055]: CLOCK: time changed from 2020-07-03 to > 2022-05-18 That's why you don't trust the GPS time until you know it has a good lock and also why you sh

time changed from 2020-07-03 to 2022-05-18

2020-07-03 Thread Udo van den Heuvel via devel
Hello, Had to reboot the box. When it came up it got the wrong date. It looks like ntpd had a role here: (...) Jul 3 10:06:47 boombox smartd[2004]: Device: /dev/sdc [SAT], not found in smartd database. Jul 3 10:06:47 boombox smartd[2004]: Device: /dev/sdc [SAT], can't monitor Current_Pending_Se