On Sun, 10 Mar 2019 18:55:29 -0400, Rich Freeman wrote: > > Mar 11 00:33:37 localhost ntpdate[4553]: Exiting, name server cannot > > be used: Temporary failure in name resolution (-3)11 Mar 00:33:37 > > ntpdate[4553]: name server cannot be used: Temporary failure in name > > resolution (-3) > > Ok, you didn't mention what you're using for a network manager. How > is the network interface being configured in the first place? There > are several ways that it is commonly done. > > Also, what are you using for DNS? In particular, are you running a > local DNS server, or are you relying on a network-supplied DNS server? > How is /etc/resolv.conf being created (likely by the network manager, > but maybe it is being done in another way).
Also, where is the NTP server? On the local network or external? > ntpdate by default depends on network-online.target and not on > nss-lookup.target, which can sometimes lead to issues if you're > running a DNS server that isn't online when the network is online > (such as a local server). The definitions of when a network is actually online are variable, see https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ You may need to add NetworkManager-wait-online.service or systemd-networkd-wait-online.service to the dependencies for ntpdate, which is possibly why Rich is asking how you manage your network. I don't use ntpdate here but systemd-timesyncd.service instead, which seems to handle this better. -- Neil Bothwick An atheist is someone who feels he has no invisible means of support.
pgpGsXVUnreSU.pgp
Description: OpenPGP digital signature
