Dear All,

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?

Thanks in advance,

Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/04/2007 05:44 PM, Paul Smith wrote:
> Dear All,
>
> 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?
>
> Thanks in advance,
>
> Paul
>

How long after the network starts does ntpd start? The network
connection might not be quite there. Maybe add a "sleep 10" to the ntpd
file in init.d?

- --

Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHVed7eERILVgMyvARAo0AAJ9ueRgUrEpBc34CAF2sdm T40z4QMwCfYHx2
MD0Aa21Lw8HqumPJ76i8qxc=
=aDHg
-----END PGP SIGNATURE-----

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, 2007-12-04 at 23:44 +0000, Paul Smith wrote:
> Dear All,
>
> 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

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Dec 4, 2007 11:50 PM, Craig White <craig@tobyhouse.com> 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/messagesec 4 20:58:14 localhost ntpdate[1943]: can't find
host ntp.ist.utl.pt
/var/log/messagesec 4 20:58:14 localhost ntpdate[1943]: no servers
can be used, exiting
/var/log/messagesec 4 20:58:14 localhost ntpd[1946]: ntpd
4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: precision = 1.000 usec
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
interface #0 wildcard, 0.0.0.0#123 Disabled
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
interface #1 wildcard, ::#123 Disabled
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
interface #2 lo, ::1#123 Enabled
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
interface #3 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
interface #4 lo, 127.0.0.1#123 Enabled
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
interface #5 vmnet1, 192.168.113.1#123 Enabled
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
interface #6 vmnet8, 192.168.139.1#123 Enabled
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: kernel time
sync status 0040
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: frequency
initialized 198.964 PPM from /var/lib/ntp/drift
/var/log/messagesec 4 20:58:14 localhost ntpd[1947]: getaddrinfo:
"ntp.ist.utl.pt" invalid host address, ignored
/var/log/messagesec 4 20:58:15 localhost ntpd[1947]: Listening on
interface #7 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
/var/log/messagesec 4 20:59:16 localhost ntpd[1947]: Cannot find
existing interface for address 193.136.134.3
/var/log/messagesec 4 20:59:16 localhost ntpd_initres[1951]: ntpd
indicates no data available!
/

Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, 2007-12-05 at 00:07 +0000, Paul Smith wrote:
> On Dec 4, 2007 11:50 PM, Craig White <craig@tobyhouse.com> 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/messagesec 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/messagesec 4 20:58:14 localhost ntpdate[1943]: no servers
> can be used, exiting
> /var/log/messagesec 4 20:58:14 localhost ntpd[1946]: ntpd
> 4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: precision = 1.000 usec
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #0 wildcard, 0.0.0.0#123 Disabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #1 wildcard, ::#123 Disabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #2 lo, ::1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #3 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #4 lo, 127.0.0.1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #5 vmnet1, 192.168.113.1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #6 vmnet8, 192.168.139.1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: kernel time
> sync status 0040
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: frequency
> initialized 198.964 PPM from /var/lib/ntp/drift
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: getaddrinfo:
> "ntp.ist.utl.pt" invalid host address, ignored

That also is weird.

> /var/log/messagesec 4 20:58:15 localhost ntpd[1947]: Listening on
> interface #7 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
> /var/log/messagesec 4 20:59:16 localhost ntpd[1947]: Cannot find
> existing interface for address 193.136.134.3
> /var/log/messagesec 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@internap.com -
- CDN Systems, Internap, Inc. http://www.internap.com -
- -
- "Do you suffer from long-term memory loss?" "I don't remember" -
- -- Chumbawumba, "Amnesia" (TubThumping) -
----------------------------------------------------------------------

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, 2007-12-05 at 00:07 +0000, Paul Smith wrote:
> On Dec 4, 2007 11:50 PM, Craig White <craig@tobyhouse.com> 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/messagesec 4 20:58:14 localhost ntpdate[1943]: can't find
> host ntp.ist.utl.pt
> /var/log/messagesec 4 20:58:14 localhost ntpdate[1943]: no servers
> can be used, exiting
> /var/log/messagesec 4 20:58:14 localhost ntpd[1946]: ntpd
> 4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: precision = 1.000 usec
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #0 wildcard, 0.0.0.0#123 Disabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #1 wildcard, ::#123 Disabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #2 lo, ::1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #3 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #4 lo, 127.0.0.1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #5 vmnet1, 192.168.113.1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> interface #6 vmnet8, 192.168.139.1#123 Enabled
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: kernel time
> sync status 0040
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: frequency
> initialized 198.964 PPM from /var/lib/ntp/drift
> /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: getaddrinfo:
> "ntp.ist.utl.pt" invalid host address, ignored
> /var/log/messagesec 4 20:58:15 localhost ntpd[1947]: Listening on
> interface #7 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
> /var/log/messagesec 4 20:59:16 localhost ntpd[1947]: Cannot find
> existing interface for address 193.136.134.3
> /var/log/messagesec 4 20:59:16 localhost ntpd_initres[1951]: ntpd
> indicates no data available!
> /
----
do you live in Portugal? (I think that's what tld=pt is)

Why are there so many interfaces? Something seems broken with your
setup. You probably should turn ipv6 off (I think you can do that in
system-config-network).

what is output of...

/sbin/ifconfig
/etc/modprobe.conf

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Dec 5, 2007 12:22 AM, Craig White <craig@tobyhouse.com> 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/messagesec 4 20:58:14 localhost ntpdate[1943]: can't find
> > host ntp.ist.utl.pt
> > /var/log/messagesec 4 20:58:14 localhost ntpdate[1943]: no servers
> > can be used, exiting
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1946]: ntpd
> > 4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: precision = 1.000 usec
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > interface #0 wildcard, 0.0.0.0#123 Disabled
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > interface #1 wildcard, ::#123 Disabled
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > interface #2 lo, ::1#123 Enabled
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > interface #3 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > interface #4 lo, 127.0.0.1#123 Enabled
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > interface #5 vmnet1, 192.168.113.1#123 Enabled
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > interface #6 vmnet8, 192.168.139.1#123 Enabled
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: kernel time
> > sync status 0040
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: frequency
> > initialized 198.964 PPM from /var/lib/ntp/drift
> > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: getaddrinfo:
> > "ntp.ist.utl.pt" invalid host address, ignored
> > /var/log/messagesec 4 20:58:15 localhost ntpd[1947]: Listening on
> > interface #7 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
> > /var/log/messagesec 4 20:59:16 localhost ntpd[1947]: Cannot find
> > existing interface for address 193.136.134.3
> > /var/log/messagesec 4 20:59:16 localhost ntpd_initres[1951]: ntpd
> > indicates no data available!
> > /
> ----
> do you live in Portugal? (I think that's what tld=pt is)
>
> Why are there so many interfaces? Something seems broken with your
> setup. You probably should turn ipv6 off (I think you can do that in
> system-config-network).
>
> what is output of...
>
> /sbin/ifconfig
> /etc/modprobe.conf

Thanks to both.

Yes, I do live in Portugal.

Answer to the other questions:

$ host ntp.ist.utl.pt
ntp.ist.utl.pt has address 193.136.134.3
$

# /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:85:38:2C:93
inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:fe38:2c93/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:69568 errors:0 dropped:0 overruns:0 frame:0
TX packets:64273 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:95856484 (91.4 MiB) TX bytes:5951540 (5.6 MiB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1010 errors:0 dropped:0 overruns:0 frame:0
TX packets:1010 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3043224 (2.9 MiB) TX bytes:3043224 (2.9 MiB)

#

# more /etc/modprobe.conf
alias eth0 tg3
alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0
#

Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, 2007-12-05 at 00:30 +0000, Paul Smith wrote:
> On Dec 5, 2007 12:22 AM, Craig White <craig@tobyhouse.com> 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/messagesec 4 20:58:14 localhost ntpdate[1943]: can't find
> > > host ntp.ist.utl.pt
> > > /var/log/messagesec 4 20:58:14 localhost ntpdate[1943]: no servers
> > > can be used, exiting
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1946]: ntpd
> > > 4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: precision = 1.000 usec
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > > interface #0 wildcard, 0.0.0.0#123 Disabled
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > > interface #1 wildcard, ::#123 Disabled
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > > interface #2 lo, ::1#123 Enabled
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > > interface #3 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > > interface #4 lo, 127.0.0.1#123 Enabled
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > > interface #5 vmnet1, 192.168.113.1#123 Enabled
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: Listening on
> > > interface #6 vmnet8, 192.168.139.1#123 Enabled
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: kernel time
> > > sync status 0040
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: frequency
> > > initialized 198.964 PPM from /var/lib/ntp/drift
> > > /var/log/messagesec 4 20:58:14 localhost ntpd[1947]: getaddrinfo:
> > > "ntp.ist.utl.pt" invalid host address, ignored
> > > /var/log/messagesec 4 20:58:15 localhost ntpd[1947]: Listening on
> > > interface #7 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
> > > /var/log/messagesec 4 20:59:16 localhost ntpd[1947]: Cannot find
> > > existing interface for address 193.136.134.3
> > > /var/log/messagesec 4 20:59:16 localhost ntpd_initres[1951]: ntpd
> > > indicates no data available!
> > > /
> > ----
> > do you live in Portugal? (I think that's what tld=pt is)
> >
> > Why are there so many interfaces? Something seems broken with your
> > setup. You probably should turn ipv6 off (I think you can do that in
> > system-config-network).
> >
> > what is output of...
> >
> > /sbin/ifconfig
> > /etc/modprobe.conf
>
> Thanks to both.
>
> Yes, I do live in Portugal.
>
> Answer to the other questions:
>
> $ host ntp.ist.utl.pt
> ntp.ist.utl.pt has address 193.136.134.3
> $
>
> # /sbin/ifconfig
> eth0 Link encap:Ethernet HWaddr 00:14:85:38:2C:93
> inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::214:85ff:fe38:2c93/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:69568 errors:0 dropped:0 overruns:0 frame:0
> TX packets:64273 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:95856484 (91.4 MiB) TX bytes:5951540 (5.6 MiB)
> Interrupt:17
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1010 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1010 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:3043224 (2.9 MiB) TX bytes:3043224 (2.9 MiB)
>
> #
>
> # more /etc/modprobe.conf
> alias eth0 tg3
> alias snd-card-0 snd-hda-intel
> options snd-card-0 index=0
> options snd-hda-intel index=0
> #
----
OK - I think Rick is onto something (DNS).

I would probably turn off ipv6 but that's me as I've seen that seriously
slow DNS queries.

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Dec 4, 2007 11:49 PM, Steven Stern <subscribed-lists@sterndata.com> 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?
>
> How long after the network starts does ntpd start? The network
> connection might not be quite there. Maybe add a "sleep 10" to the ntpd
> file in init.d?

How can I add such a sleep? Should I add the line

sleep 10

at the end of the ntpd file?

Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, 2007-12-05 at 01:24 +0000, Paul Smith wrote:
> On Dec 4, 2007 11:49 PM, Steven Stern <subscribed-lists@sterndata.com> 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?
> >
> > How long after the network starts does ntpd start? The network
> > connection might not be quite there. Maybe add a "sleep 10" to the ntpd
> > file in init.d?
>
> How can I add such a sleep? Should I add the line
>
> sleep 10
>
> at the end of the ntpd file?
----
personally, I like the idea of turning off ipv6 and rebooting better.

If you want to add the sleep 10, probably in the start section after

[ -x /usr/sbin/ntpd ] || exit 5

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list