Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Aug 2000 18:10:50 -0700
From:      "Jacob S. Barrett" <jsbarrett@acm.org>
To:        freebsd-questions@freebsd.org
Subject:   NTP and FreeBSD 4.1
Message-ID:  <3993529A.7F96AF1C@acm.org>

next in thread | raw e-mail | index | archive | help
Since I have upgraded to FreeBSD 4.1 the NTP ntpd port has stopped synching.  It
acts like it is but puts all the ntp servers on the reject list.  Are there any
known issues with ntp-4.0.99i and FreeBSD 4.1.  Under 4.0 it worked just fine.

It looks to me, but I am not 100% familiar with the correct values, that ntp is
factoring the offset times incorrectly for some reason.  Here is some debug
output to show what I mean.

ntpd -D 2:

peer 204.123.2.72 event 'event_reach' (0x84) status 'unreach, conf, 1 event,
event_reach' (0x8014)
poll_update: at 19 204.123.2.72 poll 6 burst 0 last 19 next 85
clock_filter: offset -3.185361 delay 0.044835 disp 7.937508 std 2.979632, age 0
receive: from 204.34.198.40 restrict 00
receive: at 19 from 204.34.198.40 mode 4
pkt_mode 4 action 1
peer 204.34.198.40 event 'event_reach' (0x84) status 'unreach, conf, 1 event,
event_reach' (0x8014)
poll_update: at 19 204.34.198.40 poll 6 burst 0 last 19 next 83
clock_filter: offset -3.200164 delay 0.171138 disp 7.937515 std 2.993479, age 0


ntpq:
ntpq> pe
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 bigben.cac.wash .USNO.           1 u   11   64    1   24.123  -3177.3 2972.13
 204.34.198.40   .USNO.           1 u    9   64    1  171.138  -3200.1 2993.47
 usno.pa-x.dec.c .USNO.           1 u   10   64    1   44.835  -3185.3 2979.63
 ftp06.apple.com tock.gpsclock.c  2 u   12   64    1   68.629  -3153.3 2949.71


It appears that the values like offset -3.200164 is being factored to -3200.1
which I assume is larger than the allowable offset for updating or something. 
This is really annoying me since the machine that controls time on my network
just happens to be the machine with the worse time skew problem.  I know, but it
was the machine I chose before I found that out.

If someone has any information that might be usefull please reply.

-Jake
jbarrett@amduat.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3993529A.7F96AF1C>