NTPD appears to have stopped working



  • When I first boot the system the OpenNTPD logs shows it adjusting the time. However after 20 min or so its stops. Heres my log. pfSense has been up for 2 days 16:52. I don't think my system clock is that accurate considering how much it was adjusting it by.

    Oct 7 22:46:01 ntpd[772]: adjusting local clock by 1.219621s
    Oct 7 22:41:55 ntpd[772]: adjusting local clock by 2.451878s
    Oct 7 22:38:01 ntpd[772]: adjusting local clock by 3.797804s
    Oct 7 22:34:17 ntpd[772]: adjusting local clock by 4.800844s
    Oct 7 22:31:08 ntpd[772]: adjusting local clock by 5.801608s
    Oct 7 22:27:32 ntpd[772]: adjusting local clock by 6.773254s
    Oct 7 22:23:44 ntpd[772]: adjusting local clock by 7.921526s
    Oct 7 22:19:48 ntpd[772]: adjusting local clock by 8.145950s

    If I do a ps -A it still shows the process running

    772  ??  Ss    0:01.35 ntpd: [priv] (ntpd)
      771  d0- S      0:08.33 ntpd: ntp engine (ntpd)

    So I'm not sure what to think. I ran top and the time looks close to correct, could be a few seconds off.



  • ntpd does not jump from a wrong time directly to the correct one, it adjusts small steps until it gets to the valid time. You can see that from your logs (8,7,6,5,…) so I guess it was not correct when you powered on the system but after it reached the correct time it didn't need further adjustments. I have a system with a pretty inaccurate clock and ntpd is still working after several days uptime (I have corrections about every 4 minutes). I don't think there is something wrong with ntpd. Your clock is just too good  ;)



  • @hoba:

    ntpd does not jump from a wrong time directly to the correct one, it adjusts small steps until it gets to the valid time. You can see that from your logs (8,7,6,5,…) so I guess it was not correct when you powered on the system but after it reached the correct time it didn't need further adjustments. I have a system with a pretty inaccurate clock and ntpd is still working after several days uptime (I have corrections about every 4 minutes). I don't think there is something wrong with ntpd. Your clock is just too good  ;)

    Guess so. Just seems to good to be true. The box is 166mhz Nokia IP330. Maybe since it was a network device it just has a good timeclock. However you would think it would drift slightly over 2 days.



  • When we first tested ntpd with one of my machines (an old k6-2 450MHz) we thought ntpd is not working too. We had to set incorrect times manually to see that it actually is working. Some clocks are just working properly even if you don't expect it  ;)



  • @hoba:

    When we first tested ntpd with one of my machines (an old k6-2 450MHz) we thought ntpd is not working too. We had to set incorrect times manually to see that it actually is working. Some clocks are just working properly even if you don't expect it  ;)

    Sounds good to me !


Log in to reply