I've been running an NTP server off of a Garmin GPS 18 LVC for months. None
of the software was updated or changed, and suddenly it won't sync to the
Garmin. When I start it, "ntpq -p" shows this:
remote refid st t when poll reach delay offset jitter
==============================================================================
ntp.mcast.net .MCST. 16 u - 64 0 0.000 0.000 0.000
*GPS_NMEA(1) .GPS. 0 l 5 16 177 0.000 -0.078 0.058
time-C.timefreq .ACTS. 1 u 51 64 3 34.329 989.656 0.332
india.colorado. .ACTS. 1 u 51 64 3 34.722 1012.81 0.256
ntp0.usno.navy. .USNO. 1 u 52 64 3 113.842 1007.53 0.116
ntp-nasa.arc.na .GPS. 1 u 46 64 3 19.804 999.029 0.077
After a couple minutes it shows this:
remote refid st t when poll reach delay offset jitter
==============================================================================
ntp.mcast.net .MCST. 16 u - 64 0 0.000 0.000 0.000
xGPS_NMEA(1) .GPS. 0 l 16 16 377 0.000 -0.178 0.066
-time-C.timefreq .ACTS. 1 u 43 64 17 34.006 989.736 0.153
+india.colorado. .ACTS. 1 u 46 64 17 34.764 1012.71 0.110
+tick.usno.navy. .USNO. 1 u 47 64 17 115.380 1007.88 3.442
*ntp-nasa.arc.na .GPS. 1 u 38 64 17 19.760 998.908 0.143
When I run "ntpdate -vd" from a client, I get a refusal that contains this:
198.60.22.240: Server dropped: Leap not in sync
I setup a leap file on the server and it is being loaded:
# ntpq -c "rv 0 leap,tai,leapsec,expire"
leap=11, leapsec=200901010000, expire=201206280000
This is the Garmin section of my ntp.conf:
## LinuxPPS: GPS + PPS
server 127.127.20.1 minpoll 4 prefer
fudge 127.127.20.1 flag1 1 flag2 0 time2 0.600
Still no dice. Help please?
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
