*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Hi Martin,
the fix for Bug #1575572 released yesterday turns the situation from bad
to worse from my experience. Since I saw this on i686 only before, I am
experiencing this also on amd64 since installing the init-system-helpers
update today.
| yellow Other updates (2): apt-get install init init-system-helpers
| init (1.29ubuntu1 1.29ubuntu2)
| init-system-helpers (1.29ubuntu1 1.29ubuntu2)
>From my experience this is something that happens when ntpdate isn't
ready when systemd tries to start ntpd and ntpd wasn't started before
/etc/network/if-up.d/ntpdate is started.
As far as I can see this is because /etc/network/if-up.d/ntpdate from
ntpdate and /etc/init.d/ntp from ntp try to handle each other's locks
but don't do that properly. The init.d script simply breaks the locks
from ntpdate, even if ntpdate is still running.
My workarround I had already used on Ubuntu 12.4 LTS (precise), but it
was unnecessary on Ubuntu 14.4 LTS (trusty), and now it's in again for
16.4 LTS (xenial) was to let the ifup-Script wait for the ntpd.
But that's possibly not the best solution. ;-)
For the Question why to use ntpdate *and* ntpd: We do this to immediately sync
the clocks of physical test servers (which are not always on, to save energy)
on boot, whereas during normal operation the slow drift of ntpd is the wished
behavior.
So it possibly would be a much better solution (for me) to remove
/etc/network/if-up.d/ntpdate, and start the ntpdate before ntpd from
/etc/init.d/ntp if it's present, and of course wait until it's ready
before starting ntpd.
Kind regards,
--
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:
Confirmed
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
