NTP fails to access time server on system boot.

This document (3435100) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Desktop 10

Situation

Open YaST and select Network Services-->NTP Client. Select to start the NTP daemon during boot and enter a valid NTP server either on your local intranet or the internet. Select the"Test" button to verify that it is a valid NTP server.

On system boot the NTP server will not be contacted.

Resolution

Make sure you have verified that the NTP server is valid by selecting the "Test" button in the NTP Server Configuration in YaST (as mentioned previously).

As the root user edit the file"/etc/sysconfig/network/config".

Near the end of the file you will find a line that says:

NM_ONLINE_TIMEOUT="0"

Change it to:

NM_ONLINE_TIMEOUT="30"

If the problem continues increase the timeout value by 15 and try again.

Additional Information

The following message will be reported in the /var/log/messages log:

Oct 18 13:22:55 desktop2 ntpdate[2937]: can't find host time.<timeserver>.com
Oct 18 13:22:55 desktop2 ntpdate[2937]: 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.

Disclaimer

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.