I'm seeing same behavior as Alex where failure of ntpdate is preventing
ntpd from starting. ntpdate is logging same message indicating failure
due to name resolution (Bind not running yet at boot):
Sep 16 10:40:09 scorpion ntpdate: name server cannot be used:
Temporary failure in name resolution (-3)
The script /etc/network/if-up.d/ntpdate does attempt to stop any running
ntp service prior to running ntpdate but then exits without restarting
ntp if ntpdate-debian fails.
I modified /etc/network/if-up.d/ntpdate to only log a message and exit
as a workaround and ntpd now starts at boot.
I'm still a bit puzzled why ntpd doesn't attempt to start after
/etc/network/if-up.d/ntpdate fails (multiple times in my case due to
multiple interfaces on host). When /etc/network/if-up.d/ntpdate
runs/fails, there is no log message from ntp indicating it tried to
start (neither before nor after ntpdate fails). However, after applying
my workaround, the log message for ntp service is one second after last
run of /etc/network/if-up.d/ntpdate. I would have thought that the
failure of ntpdate would not prevent the later startup of ntp. I'm
guessing that /etc/network/if-up.d/ntpdate initiates a stop in parallel
to systemd start of ntpd before it logs anything to syslog.
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ntpd not started when using ntpdate
To manage notifications about this bug go to:
ubuntu-bugs mailing list