1 |
On Sun, Mar 10, 2019 at 3:41 PM Tamer Higazi <th982a@××××××××××.com> wrote: |
2 |
|
3 |
> Mar 11 00:33:36 localhost systemd[1]: Starting Set time via NTP using |
4 |
> ntpdate... |
5 |
> Mar 11 00:33:37 localhost ntpdate[4553]: Exiting, name server cannot be |
6 |
> used: Temporary failure in name resolution (-3)11 Mar 00:33:37 |
7 |
> ntpdate[4553]: name server cannot be used: Temporary failure in name |
8 |
> resolution (-3) |
9 |
> Mar 11 00:33:37 localhost systemd[1]: ntpdate.service: Main process |
10 |
> exited, code=exited, status=1/FAILURE |
11 |
> Mar 11 00:33:37 localhost systemd[1]: ntpdate.service: Failed with |
12 |
> result 'exit-code'. |
13 |
> Mar 11 00:33:37 localhost systemd[1]: Failed to start Set time via NTP |
14 |
> using ntpdate. |
15 |
> |
16 |
|
17 |
Do you have IPV6 enabled at all on your network? I have seen problems in |
18 |
the past where the DHCP client (dhcpcd) would return as soon as it got an |
19 |
IPV6 address so processes that depended on an IPV4 address would fail to |
20 |
start - in my case I've seen it both with MySQL and with NFS mounts. |
21 |
|
22 |
The solution (if you're using dhcpcd as your DHCP client) is to add either |
23 |
|
24 |
waitip 4 |
25 |
|
26 |
or |
27 |
|
28 |
waitip 4 6 |
29 |
|
30 |
to the end of your /etc/dhcpcd.conf file. |
31 |
|
32 |
-- |
33 |
Manuel A. McLure WW1FA <manuel@××××××.org> <http://www.mclure.org> |
34 |
...for in Ulthar, according to an ancient and significant law, |
35 |
no man may kill a cat. -- H.P. Lovecraft |