On Mon, Nov 28, 2022 at 12:52:06PM +0000, MUZZULINI Frank wrote:
> Hi,
> 
> This one really puzzles me:
> MS Name/IP address         Stratum Poll Reach LastRx Last sample
> ===============================================================================
> =x 192.168.42.1                 11   5   367    38   +63.5s[ +63.5s] +/-  
> 121us
> =x 192.168.42.2                 11   6   377    78   +58.2s[ +58.2s] +/-   
> 42us
> =x 192.168.42.3                 11   7     0   799   +79.2s[ +79.2s] +/-  
> 110us
> =x 192.168.42.4                 11   8     0   84m  +112.2s[+112.2s] +/-  
> 112us
> ^x 172.16.253.1                  2  10   377  1010   +835ms[ +835ms] +/- 
> 8853us
> ^x 10.26.59.11                   1   9   377   212   +836ms[ +836ms] +/-  
> 859us
> ^x 10.26.59.12                   1   8   377   194   +836ms[ +836ms] +/-  
> 909us
> ^x 10.26.59.13                   1   8   377    22   +836ms[ +836ms] +/-  
> 838us
> 
> There are four server that agree on the correct time.
> There are also two peers which are free running just like the machine itself.
> Why is it not selecting one of the servers?

If those two unreachable sources don't become reachable, it should
eventually reach a majority and update the clock. Otherwise you would
need at least 5 working sources.

> Using stratum 11 to synchronise peers amongst each other when the uplink is 
> down is normal practice, isn't it? (It didn't seem to work here neither, but 
> this may have a good reason, these are test-VMs and they may have done wild 
> things...)

Only one source should be using the local reference unless the orphan
mode is enabled. If upstream connectivity is normally expected to
work, it's best to avoid local completely.

-- 
Miroslav Lichvar


-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Reply via email to