[ntp:questions] NTPd is not sync for some poll interval values

Harlan Stenn stenn at ntp.org
Thu Feb 5 20:55:43 UTC 2009


>>> In article <BAY104-W281F468581506F1AEC75F3DEC30 at phx.gbl>, narainmg at hotmail.com (Gaurav Narain Mathur) writes:

Gaurav> ~ $ ntpq -c "pe" remote refid st t when poll reach delay offset
Gaurav> jitter
Gaurav> =============================================================================
Gaurav> = 10.0.0.1 64.247.17.254 3 u 117 128 377 1.125 -6423.0 1427.38 ~ $
Gaurav> ntpq -c "pe" remote refid st t when poll reach delay offset jitter
Gaurav> =============================================================================
Gaurav> = 10.0.0.1 64.247.17.254 3 u 14 128 377 1.160 -8010.8 1420.48

This is a lot of jitter and a lot of offset, and the local ntpd has not
sync'd to this source.

Gaurav> $ ntpq -c "as"
Gaurav> ind assID status conf reach auth condition last_event cnt
Gaurav> =========================================================== 1 63473
Gaurav> 9014 yes yes none reject reachable 1 ~ $ ~ $ ~ $ ntpq -c "rv"
Gaurav> assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
Gaurav> version="ntpd 4.2.4p4 at 1.1520-o Wed Feb 4 21:58:44 UTC 2009 (1)",
Gaurav> processor="mips", system="Linux/2.6.26.6", leap=11, stratum=16,

"stratum 16" - the clock is not sync'd.

Gaurav> server 10.0.0.1 minpoll 7 maxpoll 8

Why are you changing these values from the default?

What happens if you leave the default values for minpoll and maxpoll?

-- 
Harlan Stenn <stenn at ntp.org>
http://ntpforum.isc.org  - be a member!




More information about the questions mailing list