Please do not blame me too hard if I provided a "patch" not in the correct format - but the script does the job for me. ntpd is started and continues to run, ntpdate seems to be invoked twice. The first invocation is too early and failes. The next one does its job but doesn't do a very impressive correction of the system time.
And here is an excerpt from my reboot log: $ grep -i ntp syslog_1743 Nov 28 17:33:49 localhost kernel: [ 0.076562] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) Nov 28 17:33:49 localhost ntpdate[781]: no servers can be used, exiting Nov 28 17:34:01 localhost systemd[1]: Starting LSB: Start NTP daemon... Nov 28 17:34:02 localhost ntp[1285]: * Starting NTP server ntpd Nov 28 17:34:02 localhost ntpd[1306]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:48 UTC 2016 (1): Starting Nov 28 17:34:02 localhost ntpd[1306]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 116:125 Nov 28 17:34:02 localhost ntp[1285]: ...done. Nov 28 17:34:02 localhost systemd[1]: Started LSB: Start NTP daemon. Nov 28 17:34:02 localhost ntpd[1309]: proto: precision = 0.129 usec (-23) Nov 28 17:34:02 localhost ntpd[1309]: restrict 0.0.0.0: KOD does nothing without LIMITED. Nov 28 17:34:02 localhost ntpd[1309]: restrict ::: KOD does nothing without LIMITED. Nov 28 17:34:02 localhost ntpd[1309]: Listen and drop on 0 v6wildcard [::]:123 Nov 28 17:34:02 localhost ntpd[1309]: Listen and drop on 1 v4wildcard 0.0.0.0:123 Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 2 lo 127.0.0.1:123 Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 3 eth0 192.168.0.12:123 Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 4 lo [::1]:123 Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 5 eth0 [fe80::221:9bff:fe4c:d684%2]:123 Nov 28 17:34:02 localhost ntpd[1309]: Listening on routing socket on fd #22 for interface updates Nov 28 17:34:05 localhost ntpdate[1154]: adjust time server 172.26.195.1 offset -0.000028 sec -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate Status in init-system-helpers package in Ubuntu: Confirmed Status in ntp package in Ubuntu: Won't Fix Bug description: After updating from 14.04 to 16.04 on a number of my systems, ntpd no longer starts at boot on any of those systems. `systemctl status ntp` shows: 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) May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon. May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon. Manually starting it using `systemctl start ntp` works fine. However, systemd does not seem to want to start it automatically at boot time. As best as I can tell based on trial and error, there is something special about the combination of the service being named "ntp.service" and the service depending on network.target. However, I haven't been able to identify exactly what is causing this. If I copy the init script to any other name, everything works fine: cp /etc/init.d/ntp /etc/init.d/ntpd Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd" systemctl enable ntpd # After a reboot, ntpd.service is started, but ntp.service is not. If I remove "$network" from the "# Required-Start: $network $remote_fs $syslog" line in /etc/init.d/ntp, then systemd starts it automatically ... But of course it is started before the network comes up, so it fails. If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot: #!/bin/sh ### BEGIN INIT INFO # Provides: ntp # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 1 # Short-Description: Start NTP daemon ### END INIT INFO echo "script was run" >> /ntp.log If I rename that same dummy script to /etc/init.d/ntp2, it is started automatically at boot. However, grepping the systemd source code and my systemd config files for ntp doesn't seem to find anything that might cause this behavior: /etc/systemd# grep -iR ntp * timesyncd.conf:#NTP= timesyncd.conf:#FallbackNTP=ntp.ubuntu.com /lib/systemd# grep -R ntp * system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd Binary file systemd-networkd matches Binary file systemd-timedated matches Binary file systemd-timesyncd matches What else can I do to debug this further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
