Ntpd not updating
Pretty sure ntpupdate is more or less depreciated depending on what version of ntp you are running. step_systime: step -191.185220 residual 0.000000 In ntp_set_tod ntp_set_tod: clock_settime: 0: Success ntp_set_tod: Final result: clock_settime: 0: Success addto_syslog: ntpd: time set -191.185220 s ntpd: time set -191.185220s filegen 2 3552675327 0 3552595200driftfile /var/lib/ntp/ntp.drift statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable server 0.server 1.server 2.server 3.server ntp.restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery The -q switch is what sets the time.
So, if you run the command without it it won't change it. Maybe if you change the default daemon options and add -q (/etc/default/ntp)?
As an example here is my output from remote refid st t when poll reach delay offset jitter ============================================================================== PRIVATE .
I am running Ubuntu on an ARM based embedded system that lacks a battery backed RTC. Thus, I use the NTP service to update the time to the current time.
When using Pi 2 or 3 time/date is not synchronizing at boot.fake-hwclock is a simple set of scripts to save the kernel's current clock periodically (including at shutdown) and restore it at boot so that the system clock keeps at least close to realtime.I am running raspbian wheezy, upgraded to all the latest packages.There's a bunch more info in the 'Pi 3 SSH over Wi Fi not working' threads in Troubleshooting. When I switched to dongle with Realtek chip I got response after about 10 seconds.I'm not familiar enough with linux routing to understand how it all fits together and what could be wrong though so haven't got any further it. @chrisoh I have similar results - zeroes for Broadcom dongle and non-zero values for Realtek.
I would check the 2 other boxes DC1 & 3 to ensure they are getting the correct time. 1 u 40 64 377 9.468 0.209 0.129 -PRIVATE3 188.8.131.52 2 u 12 64 377 6.943 -0.270 0.142 -PRIVATE5 .