ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Sat, 20 Feb 2010 22:32:01 +0100
Torfinn Ingolfsen <torfinn.ingolfsen at broadpark.no> wrote:


This output looks ... wrong ... somehow to my eyes:
root at kg-f2# date
Sat Feb 20 22:51:24 CET 2010
root at kg-f2# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*kg-omni1.kg4.no 129.240.64.3     3 u   62   64  377    0.244  597.314 360.123
root at kg-f2# ntpdc -c loopi -c sysi
offset:               0.000000 s
frequency:            500.000 ppm
poll adjust:          4
watchdog timer:       549 s
system peer:          kg-omni1.kg4.no
system peer mode:     client
leap indicator:       11
stratum:              16
precision:            -18
root distance:        0.00000 s
root dispersion:      0.00822 s
reference ID:         [10.1.10.1]
reference time:       00000000.00000000  Thu, Feb  7 2036  7:28:16.000
system flags:         auth monitor ntp kernel stats 
jitter:               0.360107 s
stability:            0.000 ppm
broadcastdelay:       0.003998 s
authdelay:            0.000000 s

Shouldn't ntpq and ntpdc be in agreement?
-- 
Torfinn