I am affected too.
Manually starting ntpd using `systemctl start ntp` doesn't work for me.
ps -ef | grep ntpd # shows no started ntpd.
systemctl status ntp # does not change active (excited), only another last line
is added.
root@ILS-AP2:~# systemctl start ntp
root@ILS-AP2:~# ps -ef | grep ntp
root 10186 10166 0 14:22 pts/6 00:00:00 grep --color=auto ntp
root@ILS-AP2:~# systemctl status ntp
● ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: active (exited) since Mi 2016-11-02 23:50:59 CET; 1 day 14h ago
Docs: man:systemd-sysv-generator(8)
Process: 1227 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
Process: 1367 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
Nov 02 23:50:59 ILS-AP2 systemd[1]: Starting LSB: Start NTP daemon...
Nov 02 23:50:59 ILS-AP2 ntp[1367]: * Starting NTP server ntpd
Nov 02 23:50:59 ILS-AP2 ntp[1367]: ...done.
Nov 02 23:50:59 ILS-AP2 ntpd[1381]: proto: precision = 0.129 usec (-23)
Nov 02 23:50:59 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 02 23:51:05 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 04 12:36:22 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 04 12:38:45 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 04 14:22:21 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
root@ILS-AP2:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
--
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 : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp