On Wed, 2007-12-05 at 00:07 +0000, Paul Smith wrote: > On Dec 4, 2007 11:50 PM, Craig White <craig@xxxxxxxxxxxxx> wrote: > > > I have NTP configured to synchronize with a server at startup, but it > > > always fails that as reported by F8 during the booting. > > > Notwithstanding: > > > > > > # /sbin/service ntpd restart > > > Shutting down ntpd: [ OK ] > > > ntpd: Synchronizing with time server: [ OK ] > > > Starting ntpd: [ OK ] > > > # > > > > > > Any ideas? > > ---- > > output of ??? > > > > cat /etc/ntp/step-tickers > > cat /etc/ntp/ntpservers > > grep server /etc/ntp.conf > > grep ntp /var/log/messages > > Thanks to both. The requested output: > > # cat /etc/ntp/step-tickers > # List of servers used for initial synchronization. > ntp.ist.utl.pt > # > > # grep server /etc/ntp.conf > # Use public servers from the pool.ntp.org project. > #broadcast 192.168.1.255 autokey # broadcast server > #broadcast 224.0.1.1 autokey # multicast server > #manycastserver 239.255.254.254 # manycast server > #server 127.127.1.0 # local clock > server ntp.ist.utl.pt > # > > # cat /etc/ntp/ntpservers > clock.redhat.com > clock2.redhat.com > # > > /var/log/messages:Dec 4 20:58:14 localhost ntpdate[1943]: can't find > host ntp.ist.utl.pt That's rather telling, isn't it? Sure smells like DNS isn't resolving. [rick@prophead ~]$ host ntp.ist.utl.pt ntp.ist.utl.pt has address 193.136.134.3 > /var/log/messages:Dec 4 20:58:14 localhost ntpdate[1943]: no servers > can be used, exiting > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1946]: ntpd > 4.2.4p2@xxxxxxxx Mon Sep 24 14:40:07 UTC 2007 (1) > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: precision = 1.000 usec > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: Listening on > interface #0 wildcard, 0.0.0.0#123 Disabled > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: Listening on > interface #1 wildcard, ::#123 Disabled > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: Listening on > interface #2 lo, ::1#123 Enabled > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: Listening on > interface #3 vmnet1, fe80::250:56ff:fec0:1#123 Enabled > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: Listening on > interface #4 lo, 127.0.0.1#123 Enabled > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: Listening on > interface #5 vmnet1, 192.168.113.1#123 Enabled > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: Listening on > interface #6 vmnet8, 192.168.139.1#123 Enabled > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: kernel time > sync status 0040 > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: frequency > initialized 198.964 PPM from /var/lib/ntp/drift > /var/log/messages:Dec 4 20:58:14 localhost ntpd[1947]: getaddrinfo: > "ntp.ist.utl.pt" invalid host address, ignored That also is weird. > /var/log/messages:Dec 4 20:58:15 localhost ntpd[1947]: Listening on > interface #7 vmnet8, fe80::250:56ff:fec0:8#123 Enabled > /var/log/messages:Dec 4 20:59:16 localhost ntpd[1947]: Cannot find > existing interface for address 193.136.134.3 > /var/log/messages:Dec 4 20:59:16 localhost ntpd_initres[1951]: ntpd > indicates no data available! ntpd is set to start pretty late in the boot process (S85ntpd), so the network should be alive and kicking. Are you sure that the network actually works and can you resolve ntp.ist.utl.pt as I did: $ host ntp.ist.utl.pt ntp.ist.utl.pt has address 193.136.134.3 Those are the first places to look. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - CDN Systems, Internap, Inc. http://www.internap.com - - - - "Do you suffer from long-term memory loss?" "I don't remember" - - -- Chumbawumba, "Amnesia" (TubThumping) - ----------------------------------------------------------------------
