Public bug reported:
We're seeing a race between if-up.d/ntpdate and the ntp startup script.
1) if-up.d/ntpdate starts.
2) if-up.d/ntpdate acquires the lock /var/lock/ntpdate-ifup.
3) if-up.d/ntpdate stops the ntp service [which isn't running anyway].
4) if-up.d/ntpdate starts running ntpdate,
In addition, /etc/dhcp/dhclient-exit-hooks.d/ntp is *also* getting in on
the act, doing an ntp restart when it sees ntp service information from
the DHCP server.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
We're seeing a possibly related problem on first boot, with more painful
consequences. Our install process does a puppet run in the late_command,
and then a reboot, and then another puppet run happens on boot.
In that first boot to the installed system, we're seeing ntp start once
and fail,
I don't think certificates are necessary here: we could permit any https
without any certificate checking, and still have an improvement, with no
additional dangers over using http. For example, you would remain
vulnerable to DNS spoofing or man-in-the-middle problems, but you would
not be subject
