Thanks for filing this bug in Ubuntu.
The logs you pasted showed ntp failing to run because something else was
listening on its socket already.
In xenial, there is a systemd service that also tries to keep the clock
accurate, called systemd-timesyncd.service. It has checks, though, to
not try to start if ntp is installed:
# systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-daemon.conf
Active: inactive (dead)
Condition: start condition failed at Ter 2017-07-11 08:55:03 BRT; 7h ago
Docs: man:systemd-timesyncd.service(8)
This is what is preventing systemd-timesyncd from running on my system, where I
have ntp installed:
# cat
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[Unit]
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService
Do you have that file
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf,
and does it have the same content as above?
Can you show the output of "sudo systemctl status systemd-
timesyncd.service"?
Assuming you can reproduce the problem at will, could you please run this
command right at the time where ntp has failed to start:
sudo fuser -v 123/udp
Thanks!
** Changed in: ntp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1703381
Title:
ntpd does not restart after failing to start upon boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1703381/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
