> 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 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 will exit instead. You will have to start it again by hand. (Or maybe systemd will restart it, but that's another problem.) I'm guessing you have a GPS unit. (Or something similar, but GPS is the most common source of non-network time.) What sort of GPS unit? gpsd? ... Things should be setup such that servers from the network sanity check your GPS clock. What's in your ntp.conf? -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel