Paul Smith wrote: > On Dec 5, 2007 2:24 PM, Paul Smith <phhs80@xxxxxxxxx> 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. > > Again, the output of 'grep ntp tail /var/log/messages': > > /var/log/messages:Dec 5 14:00:27 localhost ntpd[2928]: time reset +0.234547 s > /var/log/messages:Dec 5 14:09:42 localhost ntpd[2928]: synchronized > to 193.136.134.3, stratum 2 > /var/log/messages:Dec 5 14:26:01 localhost ntpd[2928]: ntpd exiting > on signal 15 > /var/log/messages:Dec 5 14:27:34 localhost ntpdate[1951]: can't find > host ntp.ist.utl.pt > /var/log/messages:Dec 5 14:27:34 localhost ntpdate[1951]: no servers > can be used, exiting > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1954]: ntpd > 4.2.4p2@xxxxxxxx Mon Sep 24 14:40:07 UTC 2007 (1) > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: precision = 1.000 usec > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: Listening on > interface #0 wildcard, 0.0.0.0#123 Disabled > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: Listening on > interface #1 wildcard, ::#123 Disabled > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: Listening on > interface #2 lo, ::1#123 Enabled > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: Listening on > interface #3 lo, 127.0.0.1#123 Enabled > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: Listening on > interface #4 vmnet8, 192.168.139.1#123 Enabled > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: Listening on > interface #5 vmnet1, 192.168.113.1#123 Enabled > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: kernel time > sync status 0040 > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: frequency > initialized 26.857 PPM from /var/lib/ntp/drift > /var/log/messages:Dec 5 14:27:34 localhost ntpd[1955]: getaddrinfo: > "ntp.ist.utl.pt" invalid host address, ignored > /var/log/messages:Dec 5 14:27:35 localhost ntpd[1955]: Listening on > interface #6 vmnet8, fe80::250:56ff:fec0:8#123 Enabled > /var/log/messages:Dec 5 14:27:35 localhost ntpd[1955]: Listening on > interface #7 vmnet1, fe80::250:56ff:fec0:1#123 Enabled > /var/log/messages:Dec 5 14:28:36 localhost ntpd[1955]: Cannot find > existing interface for address 193.136.134.3 > /var/log/messages:Dec 5 14:28:36 localhost ntpd_initres[1959]: ntpd > indicates no data available! > /var/log/messages:Dec 5 14:29:36 localhost ntpd[1955]: Cannot find > existing interface for address 193.136.134.3 > /var/log/messages:Dec 5 14:29:36 localhost ntpd_initres[1959]: ntpd > indicates no data available! > /var/log/messages:Dec 5 14:30:36 localhost ntpd[1955]: Cannot find > existing interface for address 193.136.134.3 > /var/log/messages:Dec 5 14:30:36 localhost ntpd_initres[1959]: ntpd > indicates no data available! > > Paul > -- Mistakes are often the stepping stones to utter failure.
