NTP fails to access time server on system boot.
This document (3435100) is provided subject to the disclaimer at the end of this document.
On system boot the NTP server will not be contacted.
As the root user edit the file"/etc/sysconfig/network/config".
Near the end of the file you will find a line that says:
Change it to:
If the problem continues increase the timeout value by 15 and try again.
Oct 18 13:22:55 desktop2 ntpdate: can't find host time.<timeserver>.com
Oct 18 13:22:55 desktop2 ntpdate: no servers can be used, exiting
Two instances of the NTP daemon will be running. When both are stopped and then the daemon is restarted the NTP server will be contacted and time will be updated correctly.
The problem happens due to a delay in the network interface being established. Increasing the timeout value of NM_ONLINE_TIMEOUT to "30" generally corrects the problem. In some circumstances the value may need to be increased even further.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3435100
- Creation Date: 19-Oct-2006
- Modified Date:10-Mar-2021
- SUSE Linux Enterprise Desktop
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com