On 05/13/2015 01:52 PM, Chandrakanth K wrote:
> bash-4.2$ ntpq -np -c assoc
> remote refid st t when poll reach delay offset jitter
> ============================================================================
> *127.127.1.0 .LOCL. 10 l 19 64 377 0.000 0.000 0.001
> 10.126.142.198 LOCAL(0) 6 u 7 16 377 0.172 859.844 0.501
> 10.126.142.204 LOCAL(0) 6 u 15 16 377 0.227 1057.22 0.240
ntpd has connected to both remote servers and retrieved data from them,
so it's not an outright packet block on some firewall. Instead ...
> ind assID status conf reach auth condition last_event cnt
> =========================================================
> 1 26554 9614 yes yes none sys.peer reachable 1
> 2 26555 9014 yes yes none reject reachable 1
> 3 26556 9014 yes yes none reject reachable 1
... it saw fit to label them as "reject"ed.
I'ld guess that the two servers having an offset of ~0.2 s with respect
to each other plays a role in that, and the client having another ~0.9 s
offset from their average might be an obstacle until you restart the
client ntpd, too.
Regards,
J. Bern
--
*NEU* - NEC IT-Infrastruktur-Produkte im <http://www.linworks-shop.de/>:
Server--Storage--Virtualisierung--Management SW--Passion for Performance
Jochen Bern, Systemingenieur --- LINworks GmbH <http://www.LINworks.de/>
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Geschäftsführer Metin Dogan, Oliver Michel
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
