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