I don't found that much about the status Outlier in NTP.
Have that status no since about some weeks periodically. But never seen before.
(https://i.ibb.co/MGdVCWg/image.png)
I'm on Business 21.10.3_1
If I interpret correctly:
If there are more than three registered servers, the worst nad surplus ones are listed as outliers.
If that's correct, I don't have to search NTP Problems at this region. We had issues on our internal systems behind the opnsense. They couldn't sync with opnsense. After a restart (@ version 21.10.3) all went fine.
reftime vs clock.. isn't reftime the time which the server "delivers"??
Because between these two examples are roughly 10 minutes..
Which would confuse me in many ways.
-
Al services looking good but "Found 1 peers, but none is suitable" ntpq -npcrv
remote refid st t when poll reach delay offset jitter
==============================================================================
10.x.x.x 195.176.26.206 2 u 945 1024 377 0.242 -0.002 0.147
associd=0 status=0058 leap_none, sync_unspec, 5 events, no_sys_peer,
version="ntpd 4.2.6p5@1.2349-o Tue Jun 23 15:38:18 UTC 2020 (1)",
processor="x86_64", system="Linux/3.10.0-1160.59.1.el7.x86_64", leap=00,
stratum=3, precision=-24, rootdelay=5.810, rootdisp=104.252,
refid=10.x.x.x,
reftime=e614d1c2.d7265bb4 Thu, Apr 28 2022 10:41:38.840,
clock=e614ddc1.df6948cf Thu, Apr 28 2022 11:32:49.872, peer=0, tc=10,
mintc=3, offset=0.063, frequency=-1.239, sys_jitter=0.000,
clk_jitter=0.131, clk_wander=0.012
Working again - nothing changed ntpq -npcrv
remote refid st t when poll reach delay offset jitter
==============================================================================
*10.x.x.x 195.176.26.206 2 u 335 1024 377 0.322 0.001 0.124
associd=0 status=0658 leap_none, sync_ntp, 5 events, no_sys_peer,
version="ntpd 4.2.6p5@1.2349-o Tue Jun 23 15:38:18 UTC 2020 (1)",
processor="x86_64", system="Linux/3.10.0-1160.59.1.el7.x86_64", leap=00,
stratum=3, precision=-24, rootdelay=5.724, rootdisp=43.500,
refid=10.x.x.x,
reftime=e614de25.c02456fe Thu, Apr 28 2022 11:34:29.750,
clock=e614df74.9025a12a Thu, Apr 28 2022 11:40:04.563, peer=13892,
tc=10, mintc=3, offset=0.001, frequency=-1.238, sys_jitter=0.000,
clk_jitter=0.125, clk_wander=0.012
further investigating necessary - and for others:
reftime = The local time, in timestamp format, when the local clock was last updated. If the local clock has never been synchronized, the value is zero.
and
https://blog.meinbergglobal.com/2021/02/25/the-root-of-all-timing-understanding-root-delay-and-root-dispersion-in-ntp/