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