I can confirm this. I have traced this a little and I believe this is what happens: Upon bringing up static network devices quite early in the boot process, the script /etc/network/if-up.d/ntpdate is executed which first stops ntpd, then calls ntpdate and then starts ntpd. Then ntpd is already running (in my case, before bind which it needs to resolve the peer IP addresses), so a later "invoke-rc.d --quiet ntp start" in the boot process does not restart ntpd, and there you go: ntpd is still in the state where it was before peer IP adresses became resolvable.
(Btw, that is also the reason why you can see ntpd stopping *before* starting in the boot process. The /etc/network/if-up.d/ntpdate is trying to stop ntpd which is not running yet.) -- ntpd starts but does not contact peers https://bugs.launchpad.net/bugs/224665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
