0
My machines with Centos refuse to sync with NTP server running on Windows AD controller. Offset value seem high and the AD presents itself as stratum 1, but in reality is stratum 4. Could this combination be the cause of my issues?
[root@centos etc]# yum list ntp
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Installed Packages
ntp.x86_64 4.2.6p5-28.el7 @rhel-7-server-rpms
[root@centos etc]# ntpq
ntpq> peer
remote refid st t when poll reach delay offset jitter
==============================================================================
192.168.16.34 .LOCL. 1 u 12 64 377 0.419 13186.1 0.910
ntpq> as
ind assid status conf reach auth condition last_event cnt
===========================================================
1 20892 9024 yes yes none reject reachable 2
ntpq> rv 20892
associd=20892 status=9024 conf, reach, sel_reject, 2 events, reachable,
srcadr=192.168.16.34, srcport=123, dstadr=192.168.16.101, dstport=123,
leap=00, stratum=1, precision=-23, rootdelay=0.000, rootdisp=10323.990,
refid=LOCL, reftime=e0d66a5e.672396dd Mon, Jul 15 2019 4:58:38.402,
rec=e0d6d7ab.3ba1c725 Mon, Jul 15 2019 12:44:59.232, reach=377,
unreach=0, hmode=3, pmode=4, hpoll=6, ppoll=6, headway=45,
flash=400 peer_dist, keyid=0, offset=13186.159, delay=0.419,
dispersion=0.966, jitter=0.910, xleave=0.109,
filtdelay= 0.42 0.42 0.42 0.45 0.46 0.46 0.41 0.45,
filtoffset= 13186.1 13185.9 13185.7 13185.5 13185.3 13185.1 13184.9 13184.7,
filtdisp= 0.00 1.01 2.01 3.02 3.98 4.97 5.94 6.92
ntpq>
I suspect it's being thrown out due to the very high
offset
- do you have the option to use some real servers who reference an external source? you host192.168.16.34
appears to be using its local clock as a time source which is not ideal. – user3788685 – 2019-07-31T17:33:26.947