On Sun, Mar 10, 2019 at 3:41 PM Tamer Higazi <th9...@googlemail.com> wrote:
> Mar 11 00:33:36 localhost systemd[1]: Starting Set time via NTP using > ntpdate... > 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) > Mar 11 00:33:37 localhost systemd[1]: ntpdate.service: Main process > exited, code=exited, status=1/FAILURE > Mar 11 00:33:37 localhost systemd[1]: ntpdate.service: Failed with > result 'exit-code'. > Mar 11 00:33:37 localhost systemd[1]: Failed to start Set time via NTP > using ntpdate. > Do you have IPV6 enabled at all on your network? I have seen problems in the past where the DHCP client (dhcpcd) would return as soon as it got an IPV6 address so processes that depended on an IPV4 address would fail to start - in my case I've seen it both with MySQL and with NFS mounts. The solution (if you're using dhcpcd as your DHCP client) is to add either waitip 4 or waitip 4 6 to the end of your /etc/dhcpcd.conf file. -- Manuel A. McLure WW1FA <man...@mclure.org> <http://www.mclure.org> ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft
