NTP fails synchronization with server at startup

[Ed Greshko]

Paul Smith wrote:

>> Why not eliminate DNS in this and use the IP address of ntp.ist.utl.pt in
>> your configuration files.  This would help narrow things down a bit.
> 
> Done, Ed. But:
> 
> /var/log/messages:Dec  5 16:12:07 localhost ntpdate[1948]: no servers
> can be used, exiting
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1951]: ntpd
> 4.2.4p2 at 1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: precision = 1.000 usec
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Listening on
> interface #0 wildcard, 0.0.0.0#123 Disabled
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Listening on
> interface #1 wildcard, ::#123 Disabled
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Listening on
> interface #2 lo, ::1#123 Enabled
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Listening on
> interface #3 lo, 127.0.0.1#123 Enabled
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Listening on
> interface #4 vmnet1, 192.168.113.1#123 Enabled
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Listening on
> interface #5 vmnet8, 192.168.139.1#123 Enabled
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: kernel time
> sync status 0040
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: frequency
> initialized 39.377 PPM from /var/lib/ntp/drift
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Cannot find
> existing interface for address 193.136.134.3
> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: configuration
> of 193.136.134.3 failed
> /var/log/messages:Dec  5 16:12:08 localhost ntpd[1952]: Listening on
> interface #6 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
> /var/log/messages:Dec  5 16:12:08 localhost ntpd[1952]: Listening on
> interface #7 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
> /var/log/messages:Dec  5 16:17:08 localhost ntpd[1952]: Listening on
> interface #8 eth0, fe80::214:85ff:fe38:2c93#123 Enabled
> /var/log/messages:Dec  5 16:17:08 localhost ntpd[1952]: Listening on
> interface #9 eth0, 192.168.1.64#123 Enabled

Ahhh....but the symptoms, or at least the messages, have changed.....

I see the line.....

> /var/log/messages:Dec  5 16:12:07 localhost ntpd[1952]: Cannot find
> existing interface for address 193.136.134.3

This seems to indicate that, at least at this point, there is no route to
193.136.134.3.  This supports the theory that the issue is a networking
issue at this point in the boot process.

There are 2 things to try to help narrow things down....

1.  Disable the vmware service from running.  You can use chkconfig to do that.

2.  Change the order of when ntpd starts.  I believe that it will be listed
as S58ntpd in /etc/rc5.d.  It is too early in the AM here....so I'm not sure
if it can be done via a GUI....but you can always move it to S98ntpd in
/etc/rc5.d.