[chrony-users] chrony startup marks all sources as falseticker

Discussion:

Alan Young

2021-04-02 14:33:26 UTC

Miroslav Lichvar

2021-04-06 08:11:40 UTC

It looks like its two vs two servers. There is no majority that could
be reached. You can try adding a third public server, so it's three vs
two, or mark one (or both) of two public server with the "trust"
option, so they can override the internal servers.
--
Miroslav Lichvar

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

Alan Young

2021-04-06 10:53:36 UTC

Permalink

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 06/04/2021 09:11, Miroslav Lichvar
wrote:<br>
</div>
<blockquote type="cite" cite="mid:***@localhost">
<pre class="moz-quote-pre" wrap="">On Fri, Apr 02, 2021 at 03:33:26PM +0100, Alan Young wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^x 199.182.221.110 2 6 0 18h -18717d[-18717d] +/- 60ms
^x 206.75.147.25 2 6 0 18h -18717d[-18717d] +/- 66ms
^x 192.168.63.114 4 6 0 18h -18717d[-18717d] +/- 1115us
^x 192.168.63.121 4 6 0 18h -18717d[-18717d] +/- 2394us

Any idea what is going on here and anything I can do to avoid and/or
correct the situation?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
It looks like its two vs two servers. There is no majority that could
be reached. You can try adding a third public server, so it's three vs
two, or mark one (or both) of two public server with the "trust"
option, so they can override the internal servers.

</pre>
</blockquote>
Thanks for the reply.<br>
<br>
Is it really the case that there is no majority? It looks to me like
all 4 servers say the same thing. It is just that they have all been
marked as falsetickers.<br>
<br>
It seems like there should be a way of clearing the falseticker
flags and re-evaluating things, especially when stuck in startup
mode.<br>
<br>
Alan.<br>
<br>
</body>
</html>

Miroslav Lichvar

2021-04-06 11:39:05 UTC

Permalink

In the provided sources output the resolution is in days, so we don't
know how much they agree. If you bring the clock closer, what does it
say for the same servers?

It seems like there should be a way of clearing the falseticker flags and
re-evaluating things, especially when stuck in startup mode.

In chrony-3.4 the initstepslew sources are added with the offline
option, so if the sources are responding, but there is no clock update
before the burst ends, it will stop polling and get stuck. You can
unstuck it with "chronyc online".

In chrony-4.0 the offline option was removed from initstepslew sources
and this shouldn't happen anymore. It should make a burst of 4
requests and then give up after another 4 requests at the 64s polling
interval.
--
Miroslav Lichvar

Alan Young

2021-04-08 11:40:08 UTC

Permalink

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 06/04/2021 12:39, Miroslav Lichvar
wrote:<br>
</div>
<blockquote type="cite" cite="mid:***@localhost">
<pre class="moz-quote-pre" wrap="">In chrony-3.4 the initstepslew sources are added with the offline
option, so if the sources are responding, but there is no clock update
before the burst ends, it will stop polling and get stuck. You can
unstuck it with "chronyc online".</pre>
</blockquote>
<br>
Thanks for this. Using "chronyc online" resolves the issue.<br>
</body>
</html>

Bill Unruh

2021-04-06 14:47:41 UTC

Permalink

Although all say it is out by 60 years, the two external are saying that that is accurate to (.06 seconds) That
is a lot. The two internal are saying that it is accurate to 1-2ms, 30 to 60 times
less than the external. Why not try what Miroslav suggests. Or, when you start
up, do a burst from some one source to get the system somewhere near the right
time (not 60 years out). Note that that "days" cannot see the actual time
difference between the two (ie, 60 years and 20ms or 60 years plus 1ms.
say). Perhaps if you showed us the chrony.conf file we might be able to give
better advice.

William G. Unruh __| Canadian Institute for|____ Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _|____ Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology |____ ***@physics.ubc.ca
Canada V6T 1Z1 ____|____ and Gravity ______|_ www.theory.physics.ubc.ca/

MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^x 199.182.221.110 2 6 0 18h -18717d[-18717d] +/- 60ms
^x 206.75.147.25 2 6 0 18h -18717d[-18717d] +/- 66ms
^x 192.168.63.114 4 6 0 18h -18717d[-18717d] +/- 1115us
^x 192.168.63.121 4 6 0 18h -18717d[-18717d] +/- 2394us
Any idea what is going on here and anything I can do to avoid and/or
correct the situation?
It looks like its two vs two servers. There is no majority that could
be reached. You can try adding a third public server, so it's three vs
two, or mark one (or both) of two public server with the "trust"
option, so they can override the internal servers.
Thanks for the reply.
Is it really the case that there is no majority? It looks to me like all 4 servers say the same thing. It is just
that they have all been marked as falsetickers.
It seems like there should be a way of clearing the falseticker flags and re-evaluating things, especially when
stuck in startup mode.
Alan.