On Dec 5, 2007 3:06 PM, Ed Greshko <Ed.Greshko@greshko.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.

Done, Ed. But:

/var/log/messagesec 5 16:12:07 localhost ntpdate[1948]: no servers
can be used, exiting
/var/log/messagesec 5 16:12:07 localhost ntpd[1951]: ntpd
4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: precision = 1.000 usec
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
interface #0 wildcard, 0.0.0.0#123 Disabled
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
interface #1 wildcard, ::#123 Disabled
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
interface #2 lo, ::1#123 Enabled
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
interface #3 lo, 127.0.0.1#123 Enabled
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
interface #4 vmnet1, 192.168.113.1#123 Enabled
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
interface #5 vmnet8, 192.168.139.1#123 Enabled
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: kernel time
sync status 0040
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: frequency
initialized 39.377 PPM from /var/lib/ntp/drift
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Cannot find
existing interface for address 193.136.134.3
/var/log/messagesec 5 16:12:07 localhost ntpd[1952]: configuration
of 193.136.134.3 failed
/var/log/messagesec 5 16:12:08 localhost ntpd[1952]: Listening on
interface #6 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
/var/log/messagesec 5 16:12:08 localhost ntpd[1952]: Listening on
interface #7 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
/var/log/messagesec 5 16:17:08 localhost ntpd[1952]: Listening on
interface #8 eth0, fe80::214:85ff:fe38:2c93#123 Enabled
/var/log/messagesec 5 16:17:08 localhost ntpd[1952]: Listening on
interface #9 eth0, 192.168.1.64#123 Enabled

Paul

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

On Wednesday 05 December 2007 15:24, Paul Smith wrote:
> 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

Hi Paul. One thing I would consider is to add some Internet time servers to
your /etc/ntp.conf. It is suggested that you have at least 3. Some
timeservers can be unreliable, or not even accessable at times, which may
well cause problems if you only have one. Make sure you use stratum 2, or 3,
not stratum 1 servers.

Another thing. Are you sure that ntp isn't doing it's stuff, even though the
bootup shows a fail. Before you do the ntpd restart, run the following as
user.

/usr/sbin/ntpq
then type pe, which will give you some info on which servers ntp is trying to
connect to, and how successfull it is being. You can keep typing pe at
intervals, which will show ntp's progress at reaching a point where a time
server is being used as a "sys peer". The server being used will be prefixed
by a "*". Other useable servers will be prefixed by a "+" "candidat". To quit
ntpq type q.

As a matter of course after receiving advice from the ntp list, I comment out
all the uncommented lines in /etc/ntp.conf, except the driftfile line,
including commenting out any server lines, as "I "select the servers I want
to use. Many of the uncommented lines are not needed, and in the case of the
restrict lines, can cause additional problems in getting ntp to work, unless
you know what you are doing.

I have had problems when I first started to use ntp. I have a few distro's
that run on the machine that gets it's time from the Internet. All use the
same 3 Internet servers. I still use FC2 for day to day use on this machine,
and do have a problem if my dialup connection isn't up when I boot FC2. The
ntp daemon dies. I have a script though that runs from rc.local. This pings a
webserver, and when the Internet connection is up, receives a response from
the ping. Then the script starts the ntp daemon, and all is ok.

My F8 install is on the other machine, and gets it's time from, in this case,
the machine that FC2 is running on. There are only 2 lines uncommented on
F8's /etc/ntp.conf. The driftfile line, and a server line, which happens to
be 192.168.0.230, and is pointing to the IP address of FC2 on the LAN.

Just for info I post a bit of output from ntpq> pe from FC2, that gets it's
time from the Internet.

/usr/sbin/ntpq
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
-crush.brunom.ne 88.191.16.241 3 u 35 256 377 138.418 36.829 21.347
+sd-881.dedibox. 193.52.184.106 2 u 38 256 377 137.545 4.407 10.555
*dedi.drazzib.co 193.49.205.17 2 u 40 256 377 145.066 10.910 24.633
+syrte8.obspm.fr 134.157.254.19 2 u 104 256 377 159.674 3.336 61.051
+ns1.kamino.fr 193.52.184.106 2 u 40 256 377 136.663 5.719 37.619
+ntp2.belbone.be 195.13.23.6 2 u 44 256 377 158.059 2.627 25.585
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
-crush.brunom.ne 88.191.16.241 3 u 224 256 377 138.418 36.829 21.347
+sd-881.dedibox. 193.52.184.106 2 u 227 256 377 137.545 4.407 10.555
*dedi.drazzib.co 193.49.205.17 2 u 230 256 377 145.066 10.910 24.633
+syrte8.obspm.fr 134.157.254.19 2 u 36 256 377 151.351 8.291 50.905
+ns1.kamino.fr 193.52.184.106 2 u 230 256 377 136.663 5.719 37.619
+ntp2.belbone.be 195.13.23.6 2 u 233 256 377 158.059 2.627 25.585
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
-crush.brunom.ne 88.191.16.241 3 u 232 256 377 138.418 36.829 38.303
+sd-881.dedibox. 193.52.184.106 2 u 236 256 377 137.545 4.407 28.083
*dedi.drazzib.co 193.49.205.17 2 u 238 256 377 145.066 10.910 26.332
+syrte8.obspm.fr 195.220.94.163 2 u 42 256 377 151.351 8.291 48.079
+ns1.kamino.fr 193.52.184.106 2 u 239 256 377 136.663 5.719 37.583
+ntp2.belbone.be 195.13.23.6 2 u 240 256 377 158.059 2.627 25.221
ntpq>

And a bit of output from ntpq> pe on F8

/usr/sbin/ntpq
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
*192.168.0.230 88.191.12.200 3 u 106 256 377 0.511 -1.245 0.353
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
*192.168.0.230 88.191.12.200 3 u 73 256 377 0.491 -0.691 0.527
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
*192.168.0.230 88.191.12.200 3 u 17 256 377 0.491 -0.691 0.533
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
*192.168.0.230 88.191.12.200 3 u 60 256 377 0.491 -0.691 0.539
ntpq>

Interestingly the refid above shows dedi.drazzib.co having an IP address
88.191.12.200, but when pinging dedi.drazzib.co from F8 at different times, I
get 2 different IP addresses, 62.210.183.19, and 62.210.183.18. This is a
good reason for using hostnames with ntp, rather than IP addresses. Hostnames
don't change, but IP addresses can.

Dont's know if any of this is usefull to you, but it's my 2¢ worth.

Nigel.









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

On Dec 5, 2007 5:17 PM, Nigel Henry <cave.dnb@tiscali.fr> wrote:
> Another thing. Are you sure that ntp isn't doing it's stuff, even though the
> bootup shows a fail. Before you do the ntpd restart, run the following as
> user.
>
> /usr/sbin/ntpq
> then type pe, which will give you some info on which servers ntp is trying to
> connect to, and how successfull it is being. You can keep typing pe at
> intervals, which will show ntp's progress at reaching a point where a time
> server is being used as a "sys peer". The server being used will be prefixed
> by a "*". Other useable servers will be prefixed by a "+" "candidat". To quit
> ntpq type q.

Thanks, Nigel. In fact,
# /usr/sbin/ntpq
ntpq> pe
No association ID's returned
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
clock-a.develoo 192.12.19.20 2 u 28 64 3 190.143 438.261 9.311
ntpq>

i.e., when I run pe after a while, I get the above, but the first time
I run pe, I get

'No association ID's returned'

Can I be sure that ntp is running now and synchronizing with a ntp server?

Paul

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

Paul Smith wrote:

>> 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/messagesec 5 16:12:07 localhost ntpdate[1948]: no servers
> can be used, exiting
> /var/log/messagesec 5 16:12:07 localhost ntpd[1951]: ntpd
> 4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: precision = 1.000 usec
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
> interface #0 wildcard, 0.0.0.0#123 Disabled
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
> interface #1 wildcard, ::#123 Disabled
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
> interface #2 lo, ::1#123 Enabled
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
> interface #3 lo, 127.0.0.1#123 Enabled
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
> interface #4 vmnet1, 192.168.113.1#123 Enabled
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Listening on
> interface #5 vmnet8, 192.168.139.1#123 Enabled
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: kernel time
> sync status 0040
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: frequency
> initialized 39.377 PPM from /var/lib/ntp/drift
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Cannot find
> existing interface for address 193.136.134.3
> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: configuration
> of 193.136.134.3 failed
> /var/log/messagesec 5 16:12:08 localhost ntpd[1952]: Listening on
> interface #6 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
> /var/log/messagesec 5 16:12:08 localhost ntpd[1952]: Listening on
> interface #7 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
> /var/log/messagesec 5 16:17:08 localhost ntpd[1952]: Listening on
> interface #8 eth0, fe80::214:85ff:fe38:2c93#123 Enabled
> /var/log/messagesec 5 16:17:08 localhost ntpd[1952]: Listening on
> interface #9 eth0, 192.168.1.64#123 Enabled

Ahhh....but the symptoms, or at least the messages, have changed.....

I see the line.....

> /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Cannot find
> existing interface for address 193.136.134.3

This seems to indicate that, at least at this point, there is no route to
193.136.134.3. This supports the theory that the issue is a networking
issue at this point in the boot process.

There are 2 things to try to help narrow things down....

1. Disable the vmware service from running. You can use chkconfig to do that.

2. Change the order of when ntpd starts. I believe that it will be listed
as S58ntpd in /etc/rc5.d. It is too early in the AM here....so I'm not sure
if it can be done via a GUI....but you can always move it to S98ntpd in
/etc/rc5.d.

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

On Dec 5, 2007 9:33 PM, Ed Greshko <Ed.Greshko@greshko.com> wrote:
> Ahhh....but the symptoms, or at least the messages, have changed.....
>
> I see the line.....
>
> > /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Cannot find
> > existing interface for address 193.136.134.3
>
> This seems to indicate that, at least at this point, there is no route to
> 193.136.134.3. This supports the theory that the issue is a networking
> issue at this point in the boot process.
>
> There are 2 things to try to help narrow things down....
>
> 1. Disable the vmware service from running. You can use chkconfig to do that.
>
> 2. Change the order of when ntpd starts. I believe that it will be listed
> as S58ntpd in /etc/rc5.d. It is too early in the AM here....so I'm not sure
> if it can be done via a GUI....but you can always move it to S98ntpd in
> /etc/rc5.d.

Operated 1 and getting:

/var/log/messagesec 5 21:41:42 localhost ntpdate[1864]: can't find
host pool.ntp.org
/var/log/messagesec 5 21:41:42 localhost ntpdate[1864]: no servers
can be used, exiting
/var/log/messagesec 5 21:41:42 localhost ntpd[1867]: ntpd
4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: precision = 1.000 usec
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: Listening on
interface #0 wildcard, 0.0.0.0#123 Disabled
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: Listening on
interface #1 wildcard, ::#123 Disabled
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: Listening on
interface #2 lo, ::1#123 Enabled
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: Listening on
interface #3 lo, 127.0.0.1#123 Enabled
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: kernel time
sync status 0040
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: frequency
initialized 66.155 PPM from /var/lib/ntp/drift
/var/log/messagesec 5 21:41:42 localhost ntpd[1868]: getaddrinfo:
"pool.ntp.org" invalid host address, ignored
/var/log/messagesec 5 21:42:44 localhost ntpd[1868]: Cannot find
existing interface for address 193.126.17.5
/var/log/messagesec 5 21:42:44 localhost ntpd_initres[1872]: ntpd
indicates no data available!
/var/log/messagesec 5 21:43:44 localhost ntpd[1868]: Cannot find
existing interface for address 193.126.17.5
/var/log/messagesec 5 21:43:44 localhost ntpd_initres[1872]: 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 Dec 5, 2007 9:33 PM, Ed Greshko <Ed.Greshko@greshko.com> wrote:
> Ahhh....but the symptoms, or at least the messages, have changed.....
>
> I see the line.....
>
> > /var/log/messagesec 5 16:12:07 localhost ntpd[1952]: Cannot find
> > existing interface for address 193.136.134.3
>
> This seems to indicate that, at least at this point, there is no route to
> 193.136.134.3. This supports the theory that the issue is a networking
> issue at this point in the boot process.
>
> There are 2 things to try to help narrow things down....
>
> 1. Disable the vmware service from running. You can use chkconfig to do that.
>
> 2. Change the order of when ntpd starts. I believe that it will be listed
> as S58ntpd in /etc/rc5.d. It is too early in the AM here....so I'm not sure
> if it can be done via a GUI....but you can always move it to S98ntpd in
> /etc/rc5.d.

Now the result to 2:

/var/log/messagesec 5 21:52:45 localhost ntpdate[2121]: can't find
host pool.ntp.org
/var/log/messagesec 5 21:52:45 localhost ntpdate[2121]: no servers
can be used, exiting
/var/log/messagesec 5 21:52:45 localhost ntpd[2127]: ntpd
4.2.4p2@1.1495-o Mon Sep 24 14:40:07 UTC 2007 (1)
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: precision = 1.000 usec
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: Listening on
interface #0 wildcard, 0.0.0.0#123 Disabled
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: Listening on
interface #1 wildcard, ::#123 Disabled
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: Listening on
interface #2 lo, ::1#123 Enabled
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: Listening on
interface #3 lo, 127.0.0.1#123 Enabled
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: kernel time
sync status 0040
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: frequency
initialized 66.155 PPM from /var/lib/ntp/drift
/var/log/messagesec 5 21:52:45 localhost ntpd[2128]: getaddrinfo:
"pool.ntp.org" invalid host address, ignored
/var/log/messagesec 5 21:53:47 localhost ntpd[2128]: Cannot find
existing interface for address 193.126.17.5
/var/log/messagesec 5 21:53:47 localhost ntpd_initres[2132]: ntpd
indicates no data available!
/var/log/messagesec 5 21:54:47 localhost ntpd[2128]: Cannot find
existing interface for address 193.126.17.5
/var/log/messagesec 5 21:54:47 localhost ntpd_initres[2132]: 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 Wednesday 05 December 2007 22:05, Paul Smith wrote:
> On Dec 5, 2007 5:17 PM, Nigel Henry <cave.dnb@tiscali.fr> wrote:
> > Another thing. Are you sure that ntp isn't doing it's stuff, even though
> > the bootup shows a fail. Before you do the ntpd restart, run the
> > following as user.
> >
> > /usr/sbin/ntpq
> > then type pe, which will give you some info on which servers ntp is
> > trying to connect to, and how successfull it is being. You can keep
> > typing pe at intervals, which will show ntp's progress at reaching a
> > point where a time server is being used as a "sys peer". The server being
> > used will be prefixed by a "*". Other useable servers will be prefixed by
> > a "+" "candidat". To quit ntpq type q.
>
> Thanks, Nigel. In fact,
> # /usr/sbin/ntpq
> ntpq> pe
> No association ID's returned
> ntpq> pe
> remote refid st t when poll reach delay offset
> jitter
> ================================================== =========================
>=== clock-a.develoo 192.12.19.20 2 u 28 64 3 190.143 438.261
> 9.311 ntpq>

Well it appears to have a connection to the timeserver here, and often takes a
while before the timeserver is accepted as a system peer. Then an "*" will
appear before clock-a.develoo. Your reach is showing as 3, and will gradually
progress until it reaches 377, but this can take some time.
>
> i.e., when I run pe after a while, I get the above, but the first time
> I run pe, I get
>
> 'No association ID's returned'

That usually indicates that ntp cannot contact the timeserver, no network
connection, or the timeserver is not accessable.
>
> Can I be sure that ntp is running now and synchronizing with a ntp server?

It appears to be running, but I think you have a problem in only having one
timeserver available.
>
> Paul

Paul. I'd still suggest that you add more timeservers to your /etc/ntp.conf.
Try the 3 that I am using. I know they are not the closest to you, but they
have been reliable for me. As I mentioned earlier, make sure that everything
in /etc/ntp.conf is commented out, except the driftfile line, comment out
also your present server, and add the ones I've listed below. Save the
changes, restart the ntp daemon, and rerun /usr/sbin/ntpq. Type pe every
minute or so, and see how it progresses.

server ntp.obspm.fr
server ntp.kamino.fr
server ntp2.belbone.be

Is this just the one machine you have connected to the Internet, or are you on
a LAN with other machines that are also using ntp to get their time from
Internet timeservers?

Nigel.

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

On Dec 5, 2007 10:12 PM, Nigel Henry <cave.dnb@tiscali.fr> wrote:
> > > Another thing. Are you sure that ntp isn't doing it's stuff, even though
> > > the bootup shows a fail. Before you do the ntpd restart, run the
> > > following as user.
> > >
> > > /usr/sbin/ntpq
> > > then type pe, which will give you some info on which servers ntp is
> > > trying to connect to, and how successfull it is being. You can keep
> > > typing pe at intervals, which will show ntp's progress at reaching a
> > > point where a time server is being used as a "sys peer". The server being
> > > used will be prefixed by a "*". Other useable servers will be prefixed by
> > > a "+" "candidat". To quit ntpq type q.
> >
> > Thanks, Nigel. In fact,
> > # /usr/sbin/ntpq
> > ntpq> pe
> > No association ID's returned
> > ntpq> pe
> > remote refid st t when poll reach delay offset
> > jitter
> > ================================================== =========================
> >=== clock-a.develoo 192.12.19.20 2 u 28 64 3 190.143 438.261
> > 9.311 ntpq>
>
> Well it appears to have a connection to the timeserver here, and often takes a
> while before the timeserver is accepted as a system peer. Then an "*" will
> appear before clock-a.develoo. Your reach is showing as 3, and will gradually
> progress until it reaches 377, but this can take some time.
> >
> > i.e., when I run pe after a while, I get the above, but the first time
> > I run pe, I get
> >
> > 'No association ID's returned'
>
> That usually indicates that ntp cannot contact the timeserver, no network
> connection, or the timeserver is not accessable.
> >
> > Can I be sure that ntp is running now and synchronizing with a ntp server?
>
> It appears to be running, but I think you have a problem in only having one
> timeserver available.
> >
> > Paul
>
> Paul. I'd still suggest that you add more timeservers to your /etc/ntp.conf.
> Try the 3 that I am using. I know they are not the closest to you, but they
> have been reliable for me. As I mentioned earlier, make sure that everything
> in /etc/ntp.conf is commented out, except the driftfile line, comment out
> also your present server, and add the ones I've listed below. Save the
> changes, restart the ntp daemon, and rerun /usr/sbin/ntpq. Type pe every
> minute or so, and see how it progresses.
>
> server ntp.obspm.fr
> server ntp.kamino.fr
> server ntp2.belbone.be
>
> Is this just the one machine you have connected to the Internet, or are you on
> a LAN with other machines that are also using ntp to get their time from
> Internet timeservers?

Thanks again, Nigel. Does it seem that it is working now?

# /usr/sbin/ntpq
ntpq> pe
remote refid st t when poll reach delay offset jitter
================================================== ============================
*syrte8.obspm.fr 134.157.254.19 2 u 27 64 377 62.413 132.612 16.037
+ns1.kamino.fr 193.52.184.106 2 u 20 64 377 85.748 119.231 10.125
+ntp2.belbone.be 195.13.23.6 2 u 54 64 377 69.566 104.344 12.046
ntpq>

No, I am directly connected to the Internet, with no LAN in between.

Paul

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

On Thursday 06 December 2007 00:07, Paul Smith wrote:
> On Dec 5, 2007 10:12 PM, Nigel Henry <cave.dnb@tiscali.fr> wrote:
> > > > Another thing. Are you sure that ntp isn't doing it's stuff, even
> > > > though the bootup shows a fail. Before you do the ntpd restart, run
> > > > the following as user.
> > > >
> > > > /usr/sbin/ntpq
> > > > then type pe, which will give you some info on which servers ntp is
> > > > trying to connect to, and how successfull it is being. You can keep
> > > > typing pe at intervals, which will show ntp's progress at reaching a
> > > > point where a time server is being used as a "sys peer". The server
> > > > being used will be prefixed by a "*". Other useable servers will be
> > > > prefixed by a "+" "candidat". To quit ntpq type q.
> > >
> > > Thanks, Nigel. In fact,
> > > # /usr/sbin/ntpq
> > > ntpq> pe
> > > No association ID's returned
> > > ntpq> pe
> > > remote refid st t when poll reach delay offset
> > > jitter
> > > ================================================== =====================
> > >==== === clock-a.develoo 192.12.19.20 2 u 28 64 3 190.143
> > > 438.261 9.311 ntpq>
> >
> > Well it appears to have a connection to the timeserver here, and often
> > takes a while before the timeserver is accepted as a system peer. Then an
> > "*" will appear before clock-a.develoo. Your reach is showing as 3, and
> > will gradually progress until it reaches 377, but this can take some
> > time.
> >
> > > i.e., when I run pe after a while, I get the above, but the first time
> > > I run pe, I get
> > >
> > > 'No association ID's returned'
> >
> > That usually indicates that ntp cannot contact the timeserver, no network
> > connection, or the timeserver is not accessable.
> >
> > > Can I be sure that ntp is running now and synchronizing with a ntp
> > > server?
> >
> > It appears to be running, but I think you have a problem in only having
> > one timeserver available.
> >
> > > Paul
> >
> > Paul. I'd still suggest that you add more timeservers to your
> > /etc/ntp.conf. Try the 3 that I am using. I know they are not the closest
> > to you, but they have been reliable for me. As I mentioned earlier, make
> > sure that everything in /etc/ntp.conf is commented out, except the
> > driftfile line, comment out also your present server, and add the ones
> > I've listed below. Save the changes, restart the ntp daemon, and rerun
> > /usr/sbin/ntpq. Type pe every minute or so, and see how it progresses.
> >
> > server ntp.obspm.fr
> > server ntp.kamino.fr
> > server ntp2.belbone.be
> >
> > Is this just the one machine you have connected to the Internet, or are
> > you on a LAN with other machines that are also using ntp to get their
> > time from Internet timeservers?
>
> Thanks again, Nigel. Does it seem that it is working now?
>
> # /usr/sbin/ntpq
> ntpq> pe
> remote refid st t when poll reach delay offset
> jitter
> ================================================== =========================
>=== *syrte8.obspm.fr 134.157.254.19 2 u 27 64 377 62.413 132.612
> 16.037 +ns1.kamino.fr 193.52.184.106 2 u 20 64 377 85.748
> 119.231 10.125 +ntp2.belbone.be 195.13.23.6 2 u 54 64 377
> 69.566 104.344 12.046 ntpq>
>
> No, I am directly connected to the Internet, with no LAN in between.
>
> Paul

That looks fine, and just what I'd expect to see.

Nigel.

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

On Dec 5, 2007 11:33 PM, Nigel Henry <cave.dnb@tiscali.fr> wrote:
> > > > > Another thing. Are you sure that ntp isn't doing it's stuff, even
> > > > > though the bootup shows a fail. Before you do the ntpd restart, run
> > > > > the following as user.
> > > > >
> > > > > /usr/sbin/ntpq
> > > > > then type pe, which will give you some info on which servers ntp is
> > > > > trying to connect to, and how successfull it is being. You can keep
> > > > > typing pe at intervals, which will show ntp's progress at reaching a
> > > > > point where a time server is being used as a "sys peer". The server
> > > > > being used will be prefixed by a "*". Other useable servers will be
> > > > > prefixed by a "+" "candidat". To quit ntpq type q.
> > > >
> > > > Thanks, Nigel. In fact,
> > > > # /usr/sbin/ntpq
> > > > ntpq> pe
> > > > No association ID's returned
> > > > ntpq> pe
> > > > remote refid st t when poll reach delay offset
> > > > jitter
> > > > ================================================== =====================
> > > >==== === clock-a.develoo 192.12.19.20 2 u 28 64 3 190.143
> > > > 438.261 9.311 ntpq>
> > >
> > > Well it appears to have a connection to the timeserver here, and often
> > > takes a while before the timeserver is accepted as a system peer. Then an
> > > "*" will appear before clock-a.develoo. Your reach is showing as 3, and
> > > will gradually progress until it reaches 377, but this can take some
> > > time.
> > >
> > > > i.e., when I run pe after a while, I get the above, but the first time
> > > > I run pe, I get
> > > >
> > > > 'No association ID's returned'
> > >
> > > That usually indicates that ntp cannot contact the timeserver, no network
> > > connection, or the timeserver is not accessable.
> > >
> > > > Can I be sure that ntp is running now and synchronizing with a ntp
> > > > server?
> > >
> > > It appears to be running, but I think you have a problem in only having
> > > one timeserver available.
> > >
> > > > Paul
> > >
> > > Paul. I'd still suggest that you add more timeservers to your
> > > /etc/ntp.conf. Try the 3 that I am using. I know they are not the closest
> > > to you, but they have been reliable for me. As I mentioned earlier, make
> > > sure that everything in /etc/ntp.conf is commented out, except the
> > > driftfile line, comment out also your present server, and add the ones
> > > I've listed below. Save the changes, restart the ntp daemon, and rerun
> > > /usr/sbin/ntpq. Type pe every minute or so, and see how it progresses.
> > >
> > > server ntp.obspm.fr
> > > server ntp.kamino.fr
> > > server ntp2.belbone.be
> > >
> > > Is this just the one machine you have connected to the Internet, or are
> > > you on a LAN with other machines that are also using ntp to get their
> > > time from Internet timeservers?
> >
> > Thanks again, Nigel. Does it seem that it is working now?
> >
> > # /usr/sbin/ntpq
> > ntpq> pe
> > remote refid st t when poll reach delay offset
> > jitter
> > ================================================== =========================
> >=== *syrte8.obspm.fr 134.157.254.19 2 u 27 64 377 62.413 132.612
> > 16.037 +ns1.kamino.fr 193.52.184.106 2 u 20 64 377 85.748
> > 119.231 10.125 +ntp2.belbone.be 195.13.23.6 2 u 54 64 377
> > 69.566 104.344 12.046 ntpq>
> >
> > No, I am directly connected to the Internet, with no LAN in between.
> >
> > Paul
>
> That looks fine, and just what I'd expect to see.

I have just noticed that at booting, the Network Manager daemon is
loaded after the ntp one. This may be the cause of the problem.

Paul

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