[ntp:questions] Rejected peers. But why?
Sander Smeenk
ssmeenk at freshdot.net
Thu Feb 5 10:46:34 UTC 2015
Hi,
On a system that has been running for quite some time now i find that
the ntpq output looks like this:
| remote refid st t when poll reach delay offset jitter
| ==============================================================================
| nscache1.dmz.bi 213.136.0.252 2 u 585 1024 377 0.614 0.058 0.310
| nscache2.dmz.bi 213.136.0.252 2 u 774 1024 377 0.414 0.116 4.459
| ntp3.dmz.bit.nl 213.136.0.252 2 u 21 1024 377 1.039 0.172 0.521
| *ntp4.bit.nl .PPS. 1 u 620 1024 377 0.701 0.126 0.131
|
| associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer,
| version="ntpd 4.2.6p3 at 1.2290-o Tue Jun 5 20:12:08 UTC 2012 (1)",
| processor="x86_64", system="Linux/3.2.0-65-generic", leap=00, stratum=2,
| precision=-22, rootdelay=0.701, rootdisp=40.953, refid=213.136.0.252,
| reftime=d87dc094.9b3384d5 Thu, Feb 5 2015 11:12:36.606,
| clock=d87dc730.0e1b8a90 Thu, Feb 5 2015 11:40:48.055, peer=19970,
| tc=10, mintc=3, offset=0.126, frequency=6.923, sys_jitter=0.131,
| clk_jitter=0.086, clk_wander=0.008
|
| ind assid status conf reach auth condition last_event cnt
| ===========================================================
| 1 19967 9014 yes yes none reject reachable 1
| 2 19968 9014 yes yes none reject reachable 1
| 3 19969 902a yes yes none reject sys_peer 2
| 4 19970 963a yes yes none sys.peer sys_peer 3
Can someone please explain why the first three peers are in 'condition:
reject' and wether or not this will recover automaticaly? The poll,
reach, delay, offset and jitter values do not seem way out of hand to
me. Why is ntpd not syncing to the three peers?
I'm fairly certain it will sync to them when i restart the process, but
for now i'll leave it like this...
Thanks,
-Sndr.
--
| 42.7 percent of all statistics are made up on the spot.
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
More information about the questions
mailing list