After upgrading to Ubuntu 16.04, I started having problems with ntp.

  1. If I put ntpdate and ntp together, then after rebooting the computer, my time is displayed incorrectly (it doesn’t fix anything at all). And service ntp status shows the following:

ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (dead) Docs: man: systemd-sysv-generator (8) Apr 24 20 : 43: 50 hp systemd [1]: Stopped LSB: Start NTP daemon. Apr 24 20:43:51 hp systemd [1]: Stopped LSB: Start NTP daemon. Apr 24 20:43:52 hp systemd [1]: Stopped LSB: Start NTP daemon.

  1. If you remove the ntpdate package, then ntp itself starts up normally, but the time is corrected only after 15 seconds, after the system has started.

How to make so that ntpdate and ntp work together and the time at start was right?

  • time is correct - do you have problems with the hardware clock? - aleksandr barakin
  • I still have windows in parallel, which the hardware clock converts in its own way, unlike Unix. Therefore, if it is normal in one OS, it is not in another. So I decided that I would set the time in Ubuntu using ntp. At 15.10 everything worked fine, now why ntp does not automatically start, I can’t understand. More precisely why ntpdata prevents it from running. - S. Nik

1 answer 1

The problem is yours, it turns out that ms / windows saves local time in the hardware clock, and gnu / linux , as it should be, saves time in utc .

output two:

  1. configure ms / windows so that it saves time, as expected, in utc .
  2. configure ubuntu to save local time in the hardware clock (add the UTC=no to the /etc/default/rcS ).
  • Yes you are right. After correcting / etc / default / rcS, the time immediately loads correctly, but ntp still does not start if ntpdate is set. I had to demolish ntpdate so that ntp worked. - S. Nik