Ronan Flood wrote: > On 28 Jul 2006 13:22:17 GMT, I wrote: > >> Jan Ceuleers <[EMAIL PROTECTED]> wrote: >> >>> So: this problem is not caused by ntptrace; the incorrect refid, stratum >>> etc. are already shown by the ntpq -n -c rv output. >> It's not a problem with ntpq either, looking at that. If ntpd is >> reporting itself as stratum-1, the refid should be the text tag of >> its refclock. If ntpd has switched sys_peer from the refclock to >> a server, it shouldn't be reporting itself as stratum-1 ... > > I can confirm this problem with ntpd-4.2.2, as I'm seeing this on one of > our GPS receivers which is having intermittent reception at the moment. > Here are ntpq -np outputs I happen to have logged from one of its peers > at consecutive two-minute intervals this morning: > > remote refid st t when poll reach delay offset jitter > > +193.62.22.74 .GPS. 1 u 20 64 377 5.780 0.087 0.055 > > -193.62.22.74 .<C1>>^Vb. 1 u 12 64 377 5.780 0.087 0.043 > > +193.62.22.74 .<C1>>^Vb. 1 u 2 64 377 5.834 0.049 0.031 > > -193.62.22.74 192.36.134.17 2 u 57 64 376 5.834 0.049 0.044 > > (<C1>>^Vb is textified ASCII of 193.62.22.98, another peer) > > Time to log a bug? >
Yes, but what does the configuration file look like and why are all those server addresses the same? Danny _______________________________________________ questions mailing list questions@lists.ntp.isc.org https://lists.ntp.isc.org/mailman/listinfo/questions
