On Monday, June 19, 2023 at 11:57:31 AM UTC, Roger wrote: > On Sun, 28 May 2023 13:43:00 -0000 (UTC), "Dave Hart" > <dave...@gmail.com> wrote: > > >I've posted a new tarball, but it may not appear for a few minutes. It > >should resolve the build failure you saw. > > > >https://people.nwtime.org/hart/ntp-dev-3792-msm-v2.tar.gz > I'm running this on my elderly system and spotted this. It was > unexpected by me but perhaps not by you. All servers at poll 10. > (Times made human readable.) > > In protostats: > > >10:00:50 185.83.169.27 0313 83 unreachable > >10:18:17 185.83.169.27 0014 84 reachable > > From peerstats before and after the above times > (offset, delay, dispersion, jitter are all *1e3 > to be human readable): > > >06:27:16 185.83.169.27 135a -0.105 12.831 15.082 0.102 > >07:02:51 185.83.169.27 135a +0.201 12.720 15.429 0.332 > >07:38:36 185.83.169.27 145a +0.178 13.003 15.495 1.392 > >10:18:17 185.83.169.27 1014 +0.196 13.226 263.647 1.646 > >10:36:15 185.83.169.27 1414 +0.002 13.057 231.781 1.556 > >11:11:00 185.83.169.27 1414 +0.115 13.215 223.162 1.601 > > Question: why wasn't this server dropped? I presume > that the reach had gone down to 0.
I think it probably was dropped, and then picked up again Notice the big jump in root dispersion in the last three lines. Also it's worth noting that manycastclient and pool associations are not demobilized when the reach register hits zero, but rather when the unreach counter hits 10 and they score the least among all associations and there are maxclock associations and there have not been any such demobilizations in the last 10 minutes (default "tos turnover 600"). Cheers, Dave Hart -- This is questions@lists.ntp.org Subscribe: questions+subscr...@lists.ntp.org Unsubscribe: questions+unsubscr...@lists.ntp.org
