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?

I don't think that's the issue. It appears the network's up. If
you do

service ntpd restart

does it come up properly? If not, do you have iptables in the way?
NTP runs on TCP/UDP port 123. You could try:

service iptables stop
service ntpd restart

If ntp comes up with that, then odds are iptables is blocking NTP
traffic and you need to run system-config-network to permit that
stuff through.

----------------------------------------------------------------------
- Rick Stevens, Principal Engineer rstevens@internap.com -
- CDN Systems, Internap, Inc. http://www.internap.com -
- -
- I.R.S.: We've got what it takes to take what you've got! -
----------------------------------------------------------------------

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

On Dec 5, 2007 1:33 AM, Craig White <craigwhite@azapple.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

I do not see any option in system-config-network to turn off ipv6.

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:45 +0000, Paul Smith wrote:
> On Dec 5, 2007 1:33 AM, Craig White <craigwhite@azapple.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
>
> I do not see any option in system-config-network to turn off ipv6.
----
try editing /etc/sysconfig/network

NETWORKING_IPV6=no

Craig

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

On Dec 5, 2007 1:51 AM, Craig White <craigwhite@azapple.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
> >
> > I do not see any option in system-config-network to turn off ipv6.
> ----
> try editing /etc/sysconfig/network
>
> NETWORKING_IPV6=no

Unfortunately, both methods (the sleep one and the ipv6 -> off one)
fail to solve the reported problem. However,

# /sbin/service ntpd restart
Shutting down ntpd: [ OK ]
ntpd: Synchronizing with time server: [ OK ]
Starting ntpd: [ OK ]
#

Paul


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 02:03 +0000, Paul Smith wrote:
> On Dec 5, 2007 1:51 AM, Craig White <craigwhite@azapple.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
> > >
> > > I do not see any option in system-config-network to turn off ipv6.
> > ----
> > try editing /etc/sysconfig/network
> >
> > NETWORKING_IPV6=no
>
> Unfortunately, both methods (the sleep one and the ipv6 -> off one)
> fail to solve the reported problem. However,
>
> # /sbin/service ntpd restart
> Shutting down ntpd: [ OK ]
> ntpd: Synchronizing with time server: [ OK ]
> Starting ntpd: [ OK ]
> #
----
you do know that you need to restart after shutting of ipv6 right?

I think that restarting ntpd seemed to work from the start.

Craig

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

On Dec 5, 2007 2:08 AM, Craig White <craigwhite@azapple.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
> > > >
> > > > I do not see any option in system-config-network to turn off ipv6.
> > > ----
> > > try editing /etc/sysconfig/network
> > >
> > > NETWORKING_IPV6=no
> >
> > Unfortunately, both methods (the sleep one and the ipv6 -> off one)
> > fail to solve the reported problem. However,
> >
> > # /sbin/service ntpd restart
> > Shutting down ntpd: [ OK ]
> > ntpd: Synchronizing with time server: [ OK ]
> > Starting ntpd: [ OK ]
> > #
> ----
> you do know that you need to restart after shutting of ipv6 right?
>
> I think that restarting ntpd seemed to work from the start.

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.

Paul

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

Paul Smith 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.
>
> Paul
>
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.)

Mikkel
--

Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

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

On Dec 5, 2007 2:09 PM, Mikkel L. Ellertson <mikkel@infinity-ltd.com> 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?

Paul

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

On Dec 5, 2007 2:24 PM, Paul Smith <phhs80@gmail.com> 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?

Again, the output of 'grep ntp tail /var/log/messages':

/var/log/messagesec 5 14:00:27 localhost ntpd[2928]: time reset +0.234547 s
/var/log/messagesec 5 14:09:42 localhost ntpd[2928]: synchronized
to 193.136.134.3, stratum 2
/var/log/messagesec 5 14:26:01 localhost ntpd[2928]: ntpd exiting
on signal 15
/var/log/messagesec 5 14:27:34 localhost ntpdate[1951]: can't find
host ntp.ist.utl.pt
/var/log/messagesec 5 14:27:34 localhost ntpdate[1951]: no servers
can be used, exiting
/var/log/messagesec 5 14:27:34 localhost ntpd[1954]: ntpd
4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: precision = 1.000 usec
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: Listening on
interface #0 wildcard, 0.0.0.0#123 Disabled
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: Listening on
interface #1 wildcard, ::#123 Disabled
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: Listening on
interface #2 lo, ::1#123 Enabled
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: Listening on
interface #3 lo, 127.0.0.1#123 Enabled
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: Listening on
interface #4 vmnet8, 192.168.139.1#123 Enabled
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: Listening on
interface #5 vmnet1, 192.168.113.1#123 Enabled
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: kernel time
sync status 0040
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: frequency
initialized 26.857 PPM from /var/lib/ntp/drift
/var/log/messagesec 5 14:27:34 localhost ntpd[1955]: getaddrinfo:
"ntp.ist.utl.pt" invalid host address, ignored
/var/log/messagesec 5 14:27:35 localhost ntpd[1955]: Listening on
interface #6 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
/var/log/messagesec 5 14:27:35 localhost ntpd[1955]: Listening on
interface #7 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
/var/log/messagesec 5 14:28:36 localhost ntpd[1955]: Cannot find
existing interface for address 193.136.134.3
/var/log/messagesec 5 14:28:36 localhost ntpd_initres[1959]: ntpd
indicates no data available!
/var/log/messagesec 5 14:29:36 localhost ntpd[1955]: Cannot find
existing interface for address 193.136.134.3
/var/log/messagesec 5 14:29:36 localhost ntpd_initres[1959]: ntpd
indicates no data available!
/var/log/messagesec 5 14:30:36 localhost ntpd[1955]: Cannot find
existing interface for address 193.136.134.3
/var/log/messagesec 5 14:30:36 localhost ntpd_initres[1959]: ntpd
indicates no data available!

Paul

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

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


--
Mistakes are often the stepping stones to utter failure.

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