Re: NTP fails synchronization with server at startup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Dec 5, 2007 3:06 PM, Ed Greshko <Ed.Greshko@xxxxxxxxxxx> wrote:
> >>>> Yes, Craig, I did reboot the computer after having turned off ipv6,
> >>>> but it did not solve the problem. It is rather strange that
> >>>> '/sbin/service ntpd restart' works perfectly and that NTP cannot
> >>>> synchronize with the server at booting.
> >>>>
> >>> This is not strange at all. When it tries to connect at boot, it can
> >>> not make the connection. When the network is up, it can make the
> >>> connection. I don't remember for sure, but I believe you were
> >>> getting a DNS error. This could be because you couldn't reach the
> >>> name server, or because you are running a local name server, and it
> >>> isn't up when NTP starts. I would also expect to see this if you
> >>> were using a wireless connection and network manager configured to
> >>> make the connection when the user logs in. (User supplied wireless
> >>> key instead of system supplied wireless key.)
> >> I understand your explanation. I do not use any wireless connection to
> >> the Internet. Moreover, my Ethernet device is configure to be
> >> activated when computer starts. What else should I look at?
>
> 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@xxxxxxxx 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

Paul


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux