[ntp:questions] ntpd stays synced after loosing gps

Николай Орехов nowhere at mail.ru
Tue May 10 09:16:22 UTC 2011


Hello!

Here's my config:

# TSIP reference clock
server 127.127.8.0 mode 138 prefer maxpoll 3
fudge 127.127.8.0 refid TSIP time1 0.08

When GPS is connected system status shows "sync_uhf_radio"
When I disconnect GPS antenna it still shows the same, however GPS marked as
"unreachable":

ntpq> pe
     remote           refid      st t when poll reach   delay   offset
 jitter
==============================================================================
*GENERIC(0)      .TSIP.           0 l  359    8    0    0.000    1.944
0.000

ntpq> ass

ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 36188  8653   yes    no  none  sys.peer unreachable  5

ntpq> rv
associd=0 status=0415 leap_none, sync_uhf_radio, 1 event, clock_sync,
version="ntpd 4.2.6p3 at 1.2290 Tue May 10 06:09:44 UTC 2011 (2)",
processor="UNKNOWN", system="QNX/6.5.0", leap=00, stratum=1,
precision=-10, rootdelay=0.000, rootdisp=20.739, refid=TSIP,
reftime=d1737f28.b8b857bd  Tue, May 10 2011 15:08:56.721,
clock=d1738091.ff8dc0aa  Tue, May 10 2011 15:14:57.998, peer=36188, tc=3,
mintc=3, offset=1.944, frequency=257.971, sys_jitter=12.296,
clk_jitter=1.084, clk_wander=0.048, tai=33, leapsec=200601010000,
expire=200806280000

ntpq> rv 36188
associd=36188 status=8653 conf, sel_sys.peer, 5 events, unreachable,
srcadr=GENERIC(0), srcport=123, dstadr=127.0.0.1, dstport=123, leap=11,
stratum=0, precision=-10, rootdelay=0.000, rootdisp=0.000, refid=TSIP,
reftime=d1737f28.00000000  Tue, May 10 2011 15:08:56.000,
rec=d1737f28.b8b857bd  Tue, May 10 2011 15:08:56.721, reach=000,
unreach=0, hmode=3, pmode=4, hpoll=3, ppoll=3, headway=0, flash=00 ok,
keyid=0, ttl=0, offset=1.944, delay=0.000, dispersion=15937.500,
jitter=0.000,
filtdelay=     0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00,
filtoffset=    0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00,
filtdisp=   16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0

ntpq> cv 36188
associd=36188 status=0043 , 4 events, clk_fault,
device="Trimble GPS (TSIP) receiver",
timecode="\x10X\x02\x05\x00'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00M->(\x00\x00\x00\x00\x00\x00M-(0\x00\x00\x00\x0fH\xff\x00\x00\x06c\x01\xff\x00\x04\x00\x0f\x10\x03",
poll=56, noreply=0, badformat=0, baddata=1, fudgetime1=80.000, stratum=0,
refid=TSIP, flags=1,
refclock_time="d1738098.47ffffe6  Tue, May 10 2011  9:15:04.281",
refclock_status="NOT SYNCHRONIZED; TIME CODE NOT CONFIRMED; TIME CODE; (LEAP
INDICATION; POSITION)",
refclock_format="Trimble TSIP",
refclock_states="NOMINAL: 00:00:56 (12.50%); *FAULT: 00:06:27 (86.38%);
ILLEGAL DATE: 00:00:05 (1.11%); running time: 00:07:28",
trimble_version="1.16 (1906/2/2)", trimble_iooptions="00 00 23 00",
trimble_satview="mode: 0x0-AUTO, PDOP 0.00, HDOP 0.00, VDOP 0.00, TDOP 0.00,
0 satellites in view: ",
trimble_receiver_health="no usable satellites, Battery backup failed,
Antenna feed line fault",
trimble_status="machine id 0x5a, Battery Powered Time Clock Fault,
Superpackets supported"

I think that condition of unreachable GPS shouldn't be sys.peer?



More information about the questions mailing list