|
|
ntp (on RH9) resets time +/- half second every 20 mins
Hi,
I am using the ntpd that came with RH9 and it seems to work except it
keeps resetting the time plus apprx half second, then 20 mins later
minus apprx half second. Can this be right? I have included below the
messags it gives in /var/messages, and the ntpd.conf is further down:
Jun 2 13:44:46 iznogood ntpd[1937]: kernel time discipline status
change 41
Jun 2 13:45:49 iznogood ntpd[1937]: kernel time discipline status
change 1
Jun 2 14:20:07 iznogood ntpd[1937]: sendto(148.167.132.201): Invalid
argument
Jun 2 14:50:06 iznogood ntpd[1937]: Connection re-established to
148.167.132.201
Jun 2 22:39:51 iznogood ntpd[1937]: time reset -0.254625 s
Jun 2 22:39:51 iznogood ntpd[1937]: synchronisation lost
Jun 2 22:59:21 iznogood ntpd[1937]: time reset 0.430880 s
Jun 2 22:59:21 iznogood ntpd[1937]: synchronisation lost
Jun 2 23:23:21 iznogood ntpd[1937]: time reset -0.812815 s
Jun 2 23:23:21 iznogood ntpd[1937]: synchronisation lost
Jun 2 23:40:45 iznogood ntpd[1937]: time reset 0.272805 s
Jun 2 23:40:45 iznogood ntpd[1937]: synchronisation lost
Jun 3 00:12:05 iznogood ntpd[1937]: time reset 0.795920 s
Jun 3 00:12:05 iznogood ntpd[1937]: synchronisation lost
Jun 3 00:35:47 iznogood ntpd[1937]: time reset 0.488954 s
Jun 3 00:35:47 iznogood ntpd[1937]: synchronisation lost
Jun 3 00:52:10 iznogood ntpd[1937]: time reset -0.597824 s
Jun 3 00:52:10 iznogood ntpd[1937]: synchronisation lost
Jun 3 01:04:00 iznogood ntpd[1937]: time reset 0.219729 s
Jun 3 01:04:00 iznogood ntpd[1937]: synchronisation lost
Jun 3 01:22:22 iznogood ntpd[1937]: time reset -0.577584 s
Jun 3 01:22:22 iznogood ntpd[1937]: synchronisation lost
Jun 3 01:46:04 iznogood ntpd[1937]: time reset 0.339956 s
Jun 3 01:46:04 iznogood ntpd[1937]: synchronisation lost
Jun 3 02:04:27 iznogood ntpd[1937]: time reset -0.401865 s
Jun 3 02:04:27 iznogood ntpd[1937]: synchronisation lost
Jun 3 02:38:46 iznogood ntpd[1937]: time reset 0.417871 s
Jun 3 02:38:46 iznogood ntpd[1937]: synchronisation lost
ntpd.conf:
restrict default ignore
restrict 127.0.0.1
restrict 192.168.10.1 mask 255.255.255.0 notrust nomodify notrap
restrict 148.167.132.201 mask 255.255.255.255 nomodify notrap noquery
server 148.167.132.201
#restrict 195.13.1.153 mask 255.255.255.255 nomodify notrap noquery
#server 195.13.1.153
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
driftfile /etc/ntp/drift
broadcastdelay 0.008
authenticate yes
keys /etc/ntp/keys
Any ideas would be greatly appreciated. thanks!
Tobias Skytte
|
|
0
|
|
|
|
Reply
|
 tobias
|
6/3/2004 8:17:45 AM |
|
Tobias Skytte wrote:
>Hi,
>I am using the ntpd that came with RH9 and it seems to work except it
>keeps resetting the time plus apprx half second, then 20 mins later
>minus apprx half second. Can this be right? I have included below the
>messags it gives in /var/messages, and the ntpd.conf is further down:
>
>Jun 2 13:44:46 iznogood ntpd[1937]: kernel time discipline status
>change 41
>Jun 2 13:45:49 iznogood ntpd[1937]: kernel time discipline status
>change 1
>Jun 2 14:20:07 iznogood ntpd[1937]: sendto(148.167.132.201): Invalid
>argument
>Jun 2 14:50:06 iznogood ntpd[1937]: Connection re-established to
>148.167.132.201
>Jun 2 22:39:51 iznogood ntpd[1937]: time reset -0.254625 s
>Jun 2 22:39:51 iznogood ntpd[1937]: synchronisation lost
>Jun 2 22:59:21 iznogood ntpd[1937]: time reset 0.430880 s
>Jun 2 22:59:21 iznogood ntpd[1937]: synchronisation lost
>Jun 2 23:23:21 iznogood ntpd[1937]: time reset -0.812815 s
>Jun 2 23:23:21 iznogood ntpd[1937]: synchronisation lost
>Jun 2 23:40:45 iznogood ntpd[1937]: time reset 0.272805 s
>Jun 2 23:40:45 iznogood ntpd[1937]: synchronisation lost
>Jun 3 00:12:05 iznogood ntpd[1937]: time reset 0.795920 s
>Jun 3 00:12:05 iznogood ntpd[1937]: synchronisation lost
>Jun 3 00:35:47 iznogood ntpd[1937]: time reset 0.488954 s
>Jun 3 00:35:47 iznogood ntpd[1937]: synchronisation lost
>Jun 3 00:52:10 iznogood ntpd[1937]: time reset -0.597824 s
>Jun 3 00:52:10 iznogood ntpd[1937]: synchronisation lost
>Jun 3 01:04:00 iznogood ntpd[1937]: time reset 0.219729 s
>Jun 3 01:04:00 iznogood ntpd[1937]: synchronisation lost
>Jun 3 01:22:22 iznogood ntpd[1937]: time reset -0.577584 s
>Jun 3 01:22:22 iznogood ntpd[1937]: synchronisation lost
>Jun 3 01:46:04 iznogood ntpd[1937]: time reset 0.339956 s
>Jun 3 01:46:04 iznogood ntpd[1937]: synchronisation lost
>Jun 3 02:04:27 iznogood ntpd[1937]: time reset -0.401865 s
>Jun 3 02:04:27 iznogood ntpd[1937]: synchronisation lost
>Jun 3 02:38:46 iznogood ntpd[1937]: time reset 0.417871 s
>Jun 3 02:38:46 iznogood ntpd[1937]: synchronisation lost
>
>ntpd.conf:
>
>restrict default ignore
>restrict 127.0.0.1
>restrict 192.168.10.1 mask 255.255.255.0 notrust nomodify notrap
>restrict 148.167.132.201 mask 255.255.255.255 nomodify notrap noquery
>server 148.167.132.201
>#restrict 195.13.1.153 mask 255.255.255.255 nomodify notrap noquery
>#server 195.13.1.153
>server 127.127.1.0 # local clock
>fudge 127.127.1.0 stratum 10
>driftfile /etc/ntp/drift
>broadcastdelay 0.008
>authenticate yes
>keys /etc/ntp/keys
>
>Any ideas would be greatly appreciated. thanks!
>
>Tobias Skytte
>
It is written that "A man who has two clocks never knows what time it is!".
I'd suggest adding a third server and perhaps even a fourth to your
ntp.conf. With four or more servers, NTP can "vote out" a server that
is keeping poor time. You'd better believe that there are such servers;
I've seen a stratum 2 server that disagreed with three others by about
140 milliseconds!
If this doesn't resolve your problem, please post the output of "ntpq -p".
|
|
|
0
|
|
|
|
Reply
|
Richard
|
6/3/2004 11:18:55 AM
|
|
On Thu, 03 Jun 2004 01:17:45 -0700, Tobias Skytte wrote:
<snip>
> Jun 3 01:22:22 iznogood ntpd[1937]: time reset -0.577584 s
> Jun 3 01:22:22 iznogood ntpd[1937]: synchronisation lost
> Jun 3 01:46:04 iznogood ntpd[1937]: time reset 0.339956 s
> Jun 3 01:46:04 iznogood ntpd[1937]: synchronisation lost
> Jun 3 02:04:27 iznogood ntpd[1937]: time reset -0.401865 s
> Jun 3 02:04:27 iznogood ntpd[1937]: synchronisation lost
> Jun 3 02:38:46 iznogood ntpd[1937]: time reset 0.417871 s
> Jun 3 02:38:46 iznogood ntpd[1937]: synchronisation lost
I have seen this happen on one of my machines. That was a
laptop. I presume it had something to do with power saving
modes of the BIOS.
I happened to notice this problem disappeared when xosview
was running. So now I have a X-server without window manager
operational only to have xosview running.
<snip>
> Any ideas would be greatly appreciated. thanks!
So, what kind of computer are you using?
>
> Tobias Skytte
Regards, Johan
|
|
|
0
|
|
|
|
Reply
|
Johan
|
6/3/2004 9:29:32 PM
|
|
|
2 Replies
250 Views
(page loaded in 0.071 seconds)
Similiar Articles: ntp (on RH9) resets time +/- half second every 20 mins - comp ...Hi, I am using the ntpd that came with RH9 and it seems to work except it keeps resetting the time plus apprx half second, then 20 mins later minus ap... comp.protocols.time.ntp - page 54ntp (on RH9) resets time +/- half second every 20 mins 2 118 (6/3/2004 8:17:45 AM) Hi, I am using the ntpd that came with RH9 and it seems to work except it keeps ... /etc/ntp/keys - comp.protocols.time.ntpntp (on RH9) resets time +/- half second every 20 mins - comp ..... 153 server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift ... kernel time discipline status codes - comp.protocols.time.ntp ...ntp (on RH9) resets time +/- half second every 20 mins - comp ... kernel time discipline status codes - comp.protocols.time.ntp ... ntp (on RH9) resets time +/- half ... synchronisation lost - comp.protocols.time.ntpntp (on RH9) resets time +/- half second every 20 mins - comp ..... 1937]: Connection re-established to 148.167.132.201 Jun 2 22:39:51 iznogood ntpd[1937]: time reset -0 ... ntpd vs ntpq!!!!! - comp.protocols.time.ntpntp (on RH9) resets time +/- half second every 20 mins - comp ... Hi, I am using the ntpd that came with RH9 and it seems to work except it keeps ... ntpd vs ntpq ... Stratum goes back to 16 all the time - comp.protocols.time.ntp ...ntp (on RH9) resets time +/- half second every 20 mins - comp ... Stratum goes back to 16 all the time - comp.protocols.time.ntp ... Then, after a couple of minutes, it ... Leap Second - comp.protocols.time.ntpOn 2 d=E9c, 20:22, Unruh <unruh ... warning of an impending leap second to be inserted/deleted in the last minute ... Leap Second - comp.protocols.time.ntp Hi all, Since yesterday ... Leap second bug? - comp.protocols.time.ntpntp (on RH9) resets time +/- half second every 20 mins - comp ... Leap Second - comp.protocols.time.ntp On 2 d=E9c, 20:22, Unruh ... of an impending leap second to be ... time reset, syncronisation lost and Large PPM values - comp ...... bothers ntpd so it looses sync about every half ... Oct 20 16:09:31 srv3 ntpd[20655]: time reset +0.683516 s >Oct 20 16 ... Re: galaxy node reboot after ntp time reset «A ... ntp (on RH9) resets time +/- half second every 20 mins - comp ...Hi, I am using the ntpd that came with RH9 and it seems to work except it keeps resetting the time plus apprx half second, then 20 mins later minus ap... comp.protocols.time.ntp - page 54 | Computer Groupntp (on RH9) resets time +/- half second every 20 mins 2 118 (6/3/2004 8:17:45 AM) Hi, I am using the ntpd that came with RH9 and it seems to work except it keeps ... 7/24/2012 4:57:50 AM
|
|
|
|
|
|
|
|
|
Search |
Post Question |
Groups |
Stream |
About |
Register
2 followers. 