Ubuntu ntp not updating time
ntpdate, if installed, will run it once at boot time to set up your time according to Ubuntu's NTP server.However, a system's clock is likely to drift considerably between reboots if the time between reboots is long.
This is most likely only a recent problem since I had power failures before and never noticed problems with time. When I stop the service and run ntpd manually May 5 autohome ntpd: ntpd [email protected] Fri May 18 UTC 2012 (1) May 5 autohome ntpd: proto: precision = 1.000 usec May 5 autohome ntpd: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 May 5 autohome ntpd: Listen normally on 1 lo 127.0.0.1 UDP 123 May 5 autohome ntpd: Listen normally on 2 eth0 192.168.1.120 UDP 123 May 5 autohome ntpd: peers refreshed May 5 autohome ntpd: Listening on routing socket on fd #19 for interface updates # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged.Your server will # pick a different set every time it starts up.Please consider joining the # pool: server 0.iburst server 1.iburst server 2.iburst server 3.iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/for # details. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers.ntpdate is a bit of a blunt instrument as it can only adjust the time once a day in one big correction.The ntp daemon ntpd is far more subtle as it calculates the drift of your system clock and continuously adjusts it in small increments.