On 2011-12-01, Pete Ashdown <[email protected]> wrote: > unruh <[email protected]> writes: > >>If he has peerstats log file, he can look at it and see what teh offset >>is of the oncore and the other ntp sources to see if it is really >>misbehaving that badly. Also, if it is out by 16 sec, why in the world >>has ntp not stepped the time? The threshold is 128ms. > > Here is another run with my clockstats and peerstats files. Any help in > isolating this problem is much appreciated. > > clockstats: > > 55896 12852.469 127.127.30.0 ONCORE[0]: ONCORE DRIVER -- CONFIGURING > 55896 12852.469 127.127.30.0 ONCORE[0]: state = ONCORE_NO_IDEA > 55896 12852.470 127.127.30.0 ONCORE[0]: Input mode = 1 > 55896 12852.470 127.127.30.0 ONCORE[0]: Initializing timing to Assert. > 55896 12852.470 127.127.30.0 ONCORE[0]: HARDPPS Set. > 55896 12852.470 127.127.30.0 ONCORE[0]: ONCORE: Can't open SHMEM file > 55896 12852.470 127.127.30.0 ONCORE[0]: SHMEM (size = 3628) is CONFIGURED and > available as /var/log/ntp/oncore.0 > 55896 12852.470 127.127.30.0 ONCORE[0]: state = ONCORE_CHECK_ID > 55896 12853.463 127.127.30.0 ONCORE[0]: Oncore: Resend @@Cj > 55896 12853.597 127.127.30.0 ONCORE[0]: @@Cj > 55896 12853.597 127.127.30.0 ONCORE[0]: COPYRIGHT 1991-1997 MOTOROLA INC. > 55896 12853.597 127.127.30.0 ONCORE[0]: SFTW P/N # 98-P36848P > 55896 12853.597 127.127.30.0 ONCORE[0]: SOFTWARE VER # 3 > 55896 12853.597 127.127.30.0 ONCORE[0]: SOFTWARE REV # 2 > 55896 12853.597 127.127.30.0 ONCORE[0]: SOFTWARE DATE Aug 23 2000 > 55896 12853.598 127.127.30.0 ONCORE[0]: MODEL # R5222U1115 > 55896 12853.598 127.127.30.0 ONCORE[0]: HWDR P/N # 5 > 55896 12853.598 127.127.30.0 ONCORE[0]: SERIAL # R0C83D > 55896 12853.598 127.127.30.0 ONCORE[0]: MANUFACTUR DATE 1K31 > 55896 12853.598 127.127.30.0 ONCORE[0]: > 55896 12853.598 127.127.30.0 ONCORE[0]: This looks like an Oncore UT with > version 3.2 firmware. > 55896 12853.598 127.127.30.0 ONCORE[0]: Channels = 8, TRAIM = ON > 55896 12853.598 127.127.30.0 ONCORE[0]: state = ONCORE_CHECK_CHAN > 55896 12858.142 127.127.30.0 ONCORE[0]: Input says chan = -1 > 55896 12858.142 127.127.30.0 ONCORE[0]: Model # says chan = 8 > 55896 12858.142 127.127.30.0 ONCORE[0]: Testing says chan = 8 > 55896 12858.142 127.127.30.0 ONCORE[0]: Using chan = 8 > 55896 12858.142 127.127.30.0 ONCORE[0]: state = ONCORE_HAVE_CHAN > 55896 12859.593 127.127.30.0 ONCORE[0]: state = ONCORE_TEST_SENT > 55896 12866.441 127.127.30.0 ONCORE[0]: GPS antenna: OK > 55896 12866.441 127.127.30.0 ONCORE[0]: state = ONCORE_INIT > 55896 12869.411 127.127.30.0 ONCORE[0]: Setting Posn from input data > 55896 12869.411 127.127.30.0 ONCORE[0]: state = ONCORE_ALMANAC > 55896 12877.550 127.127.30.0 ONCORE[0]: Posn: > 55896 12877.550 127.127.30.0 ONCORE[0]: Lat = N 40.7610850deg, Long = W > 111.8890642deg, Alt = 1298.83m (4261.25ft) GPS > 55896 12877.551 127.127.30.0 ONCORE[0]: Lat = N 40deg 45.6651m, Long = W > 111deg 53.34385m, Alt = 1298.83m (4261.25ft) GPS > 55896 12877.551 127.127.30.0 ONCORE[0]: Lat = N 40deg 45m 39.91s, Long = W > 111deg 53m 20.63s, Alt = 1298.83m (4261.25ft) GPS > 55896 12877.609 127.127.30.0 ONCORE[0]: Cable delay is set to 50 ns > 55896 12877.618 127.127.30.0 ONCORE[0]: Satellite mask angle set to 0 degrees > 55896 12880.018 127.127.30.0 ONCORE[0]: Have now loaded an ALMANAC > 55896 12880.018 127.127.30.0 ONCORE[0]: state = ONCORE_RUN > 55896 12880.019 127.127.30.0 ONCORE[0]: SSstate = ONCORE_SS_DONE > 55896 12880.091 127.127.30.0 ONCORE[0]: ONCORE: Detected TRAIM, TRAIM = ON > 55896 12880.091 127.127.30.0 ONCORE[0]: Input says TRAIM = -1 > 55896 12880.091 127.127.30.0 ONCORE[0]: Model # says TRAIM = 1 > 55896 12880.091 127.127.30.0 ONCORE[0]: Testing says TRAIM = 1 > 55896 12880.091 127.127.30.0 ONCORE[0]: Using TRAIM = 1 > 55896 12881.120 127.127.30.0 ONCORE[0]: PPS Offset is set to 0 ns > 55896 12881.136 127.127.30.0 ONCORE[0]: Satellite mask angle is 0 degrees > 55896 12882.131 127.127.30.0 ONCORE[0]: Leap Sec Msg: 15 15 2013 11 28 15 0 0 > 0 0 > 55896 12882.131 127.127.30.0 ONCORE[0]: Set pp.leap to LEAP_NOWARNING > 55896 12896.293 127.127.30.0 3531699260.000011567 2011 335 3 34 56 20 rstat > 08 dop 0.0 nsat 11,5 traim 1,0,1 sigma 77 neg-sawtooth -30 sat 88808008
If the above really is the one that occured just before the next one, then that oncore device is completely nuts. > 55896 12933.292 127.127.30.0 3531699333.000052836 2011 335 3 34 57 33 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 49 neg-sawtooth 37 sat 88808508 > 55896 12935.228 127.127.30.0 3531699334.000053055 2011 335 3 34 59 34 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 49 neg-sawtooth -30 sat 88808508 > 55896 12936.217 127.127.30.0 3531699336.000057251 2011 335 3 35 0 36 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 49 neg-sawtooth 35 sat 88808808 > 55896 12937.217 127.127.30.0 3531699337.000059778 2011 335 3 35 1 37 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth -3 sat 88808808 > 55896 12938.218 127.127.30.0 3531699338.000064562 2011 335 3 35 2 38 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth -40 sat 88808808 > 55896 12939.223 127.127.30.0 3531699339.000062676 2011 335 3 35 3 39 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth 28 sat 88808808 > 55896 12940.218 127.127.30.0 3531699340.000063985 2011 335 3 35 4 40 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth -8 sat 88808808 > 55896 12941.218 127.127.30.0 3531699341.000066038 2011 335 3 35 5 41 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth -44 sat 88808808 > 55896 12942.218 127.127.30.0 3531699342.000068975 2011 335 3 35 6 42 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth 23 sat 88808808 > 55896 12943.218 127.127.30.0 3531699343.000071365 2011 335 3 35 7 43 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth -13 sat 88808808 > 55896 12944.233 127.127.30.0 3531699344.000071808 2011 335 3 35 8 44 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth -49 sat 88808808 > 55896 12945.217 127.127.30.0 3531699345.000073456 2011 335 3 35 9 45 rstat > 08 dop 0.0 nsat 11,6 traim 1,0,0 sigma 44 neg-sawtooth 18 sat 88838808 > 55896 12946.216 127.127.30.0 3531699346.000075285 2011 335 3 35 10 46 rstat > 08 dop 0.0 nsat 11,7 traim 1,0,0 sigma 44 neg-sawtooth -18 sat 88858808 > > > peerstats: > > 55896 12854.501 132.163.4.103 9024 -0.011812283 0.037626143 7.937500402 > 0.000000238 > 55896 12855.483 198.123.30.132 9024 -0.000936135 0.019738902 7.937507897 > 0.000000238 > 55896 12856.485 204.152.184.72 9024 0.001482225 0.021338600 7.937501233 > 0.000000238 > 55896 12896.293 127.127.30.0 9024 35.999988432 0.000000000 7.937500119 > 0.000000238 > 55896 12932.483 198.123.30.132 9014 -36.001000457 0.019782984 7.937507897 > 0.000000238 > 55896 12933.292 127.127.30.0 9044 -36.000052837 0.000000000 7.937500119 > 0.000000238 > 55896 12934.485 204.152.184.72 9014 -35.998534232 0.021388051 7.937501233 > 0.000000238 > 55896 12934.501 132.163.4.103 9014 -36.012125275 0.037840698 7.937500404 > 0.000000238 OK, this is absurd. There is something totally wrong with your gps. It starts off at 36 seconds off the correct time ( as indicated by the network offsets). ntp then jump sets the time to -36 sec off. The gps then gtives a much more reasonable time. But it has managed to totally confuse ntpd and started it seriously on the wrong track as far as the drift is concerned. I would throw away that gps unit, or figure out what is going wrong. It should not be jumping around by 10's of seconds, no matter what the excuse. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
