[Bug 1577596] Re: ntpd not started by systemd
1577596 at bugs.launchpad.net
Tue May 3 10:49:08 UTC 2016
** Changed in: ntp (Ubuntu)
Importance: Undecided => High
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
ntpd not started by systemd
Status in ntp package in Ubuntu:
Status in systemd package in Ubuntu:
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)
May 02 19:10:14 host systemd: Stopped LSB: Start NTP daemon.
May 02 19:10:17 host systemd: 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
If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot:
### 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 *
/lib/systemd# grep -R ntp *
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:
More information about the foundations-bugs