On 31 Dec 2005 08:01:06 -0800, "wa6zvp" <[EMAIL PROTECTED]> wrote for the entire planet to see:
> >Wolfgang S. Rupprecht wrote: >> Can someone shed any light on what is going on here? Could >> clock.sjc.he.net have jumped the gun and inserted a leap second a day >> early? I've never seen it off by more than a millisecond or two >> before and the offset of almost exactly a second is very suspicious, >> especially since we are so close to a leap second event. >> >> remote refid st t when poll reach delay offset >> jitter >> ============================================================================== >> *GPS_ONCORE(0) .GPS. 0 l 14 16 377 0.000 0.004 >> 0.002 >> -bonnet.wsrcc.co 25.96.172.67 2 u 34 64 377 0.250 -0.473 >> 0.390 >> xclock.sjc.he.ne .CDMA. 1 u 7 64 377 15.278 -999.34 >> 0.953 >> LOCAL(0) LOCAL(0) 10 l 45 64 377 0.000 0.000 >> 0.001 >> >> -wolfgang >> -- >> Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/ >> Direct SIP URL Dialing: http://www.wsrcc.com/wolfgang/phonedirectory.html > >Sure looks like a software bug in the reference clock. They do not >have additional backup references >to protect against false ticking. Here is the current status: > >$ ntpq -c cv clock.sjc.he.net >status=0606 clk_badtime, last_clk_badtime >device="EndRun Technologies Praecis CDMA", >timecode="2005 365 15:41:02.644978", poll=415464, noreply=1, >badformat=0, baddata=1, fudgetime1=0.000, stratum=0, refid=CDMA, >flags=2 > >I suppose it could be an error in the actual reference clock in the >cellsite this thing >is listening to which is likely a GPS rcvr. > >Humm. . . My PCS phone is a second slow right now, but I've never >actually >checked it to the second before. . . > > Roger (at hmc.edu) Big problem here too... I'm assuming for now that the other stratum 1s are correct and my CDMA receiver has a problem. Any info would be appreciated. />ntpx ntp0.jrc.us status=04f4 leap_none, sync_uhf_clock, 15 events, event_peer/strat_chg, version="ntpd [EMAIL PROTECTED] Apr 12 14:10:45 (UTC+02:00) 2005 (12)", processor="unknown", system="WINDOWS/NT", leap=00, stratum=1, precision=-19, rootdelay=0.000, rootdispersion=0.373, peer=16532, refid=CDMA, reftime=c7612da1.127bedef Sat, Dec 31 2005 11:17:37.072, poll=4, clock=c7612da8.097d8486 Sat, Dec 31 2005 11:17:44.037, state=4, offset=0.027, frequency=14.157, jitter=0.013, noise=0.002, stability=0.000 remote refid st t when poll reach delay offset jitter ============================================================================== *GPS_PALISADE(1) .CDMA. 0 l 7 16 377 0.000 0.027 0.013 ntsrv08.jrc.lan ntsrv04.jrc.lan 2 u 4 16 377 0.848 0.017 0.028 ntsrv05.jrc.lan ntsrv04.jrc.lan 2 u 2 16 377 0.908 -1.764 0.610 xnavobs1.mit.edu .PSC. 1 u 311 512 377 11.601 999.873 0.168 and ... />ntpx tick.jrc.us status=0600 leap_none, sync_ntp, no events, event_unspec, system="cisco", leap=00, stratum=2, rootdelay=3.950, rootdispersion=1.220, peer=46639, refid=ns1.jrc.us, reftime=c7612e21.4f43fce7 Sat, Dec 31 2005 11:19:45.309, poll=10, clock=c7612e38.fbbdcf49 Sat, Dec 31 2005 11:20:08.983, phase=-0.395, freq=208.54, error=0.35 remote refid st t when poll reach delay offset jitter ============================================================================== +c3620-u5.jensen nt4b.jrc.lan 2 u 170 1024 377 5.660 -0.410 0.210 -ns2.jensenresea ntsrv04.jrc.lan 2 - 8 1024 377 4.170 -1.591 0.430 *ns1.jrc.us .CDMA. 1 - 24 1024 377 3.950 -0.395 0.140 +mail.jensenrese ntsrv04.jrc.lan 2 - 245 1024 377 3.280 -0.348 0.180 +c2620-u7.jrc.la ns1.jrc.us 2 u 47 1024 377 4.530 -0.652 0.240 -vpn.jensenresea ntsrv04.jrc.lan 2 - 1016 1024 377 4.490 1.683 1.170 xtoshi.keneli.or .GPS. 1 - 5 1024 377 20.870 999.165 0.530 xntp-4.cns.vt.ed timelord.cns.vt 2 - 1022 1024 377 20.950 998.995 0.550 +gw-eth1.jrc.lan ns1.jrc.us 2 u 256 1024 377 6.160 -0.919 0.700 _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
