*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
I don't think this is a duplicate of bug #1575572
I am seeing this problem on an Ubuntu 16.04 machine that has the update "This
bug was fixed in the package init-system-helpers - 1.29ubuntu2" mentioned as
being a fix for that bug but ntpd is still broken on booting. I am seeing this:
Jul 12 14:14:43 metop ntpd[1933]: unable to bind to wildcard address :: -
another process may be running - EXITING
Jul 12 14:14:50 metop ntpdate[1758]: step time server 134.36.22.27 offset
0.264278 sec
So basically the systemd dependency arrangement is broken: ntpdate is
slow now (as for comment #16 above) and not exiting before ntpd is
started, it then it fails due to ntpdate still running.
A later manual start of ntpd works fine, but that is not an acceptable
situation for machines that are unattended and/or used by people that
don't have administrative rights (or knowledge) to manually start ntpd
later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577596
Title:
ntpd not started when using ntpdate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
