[ntp:questions] why is my pool server's offset so bad

Dennis Hilberg, Jr. timekeeper at dennishilberg.com.invalid
Thu Jan 31 06:07:58 UTC 2008


Pat Farrell wrote:
> Well, its gotten bad again. I had it working well for a few days.
> But lately, the offsets are diving down. See
> http://www.pool.ntp.org/scores/70.184.242.241
> 
> Clearly something is wrong.
> 
> Thanks
> pat

saturn:$ ntpq -p 70.184.242.241
    remote           refid      st t when poll reach   delay   offset  jitter
============================================================================
ntp-2.cns.vt.ed 198.82.247.40   2 u  32h   64    0   17.908   -0.296   0.000
ntp-4.cns.vt.ed 198.82.247.164  2 u  32h   64    0   18.567    0.637   0.000
ancalagon.cede. .INIT.         16 u    - 1024    0    0.000    0.000   0.000
prometheus.acm. .Ïôð.          16 u  32h   64    0    0.000    0.000   0.000
time-b.nist.gov .ACTS.          1 u  32h   64    0   13.555    6.162   0.000

The reachability column for each upstream server is at zero, indicating that 
ntpd can't connect to those servers.  Your system clock has been wandering 
for approx. the last 32 hours, which is about the same time your offset 
history began to take a dive.

Have you inadvertently blocked outbound traffic on 123/UDP?  I can query 
your server just fine, so inbound is not a problem.

-- 
Dennis Hilberg, Jr.     \  timekeeper(at)dennishilberg(dot)com
NTP Server Information:  \  http://saturn.dennishilberg.com/ntp.php




More information about the questions mailing list