Re: [chrony-users] repeating "Can't synchronise: no selectable sources" log msgs ... but sources _are_ selected, and chrony _is_ sync'd. (mis)config or bug?

[Bill Unruh <unruh@xxxxxxxxxxxxxx>]

On Fri, 9 Oct 2020, PGNet Dev wrote:

> I run client
>
> 	chronyd --version
> 		chronyd (chrony) version 4.0 (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG)
>
> local config is
>
> 	cat /etc/chrony.conf
> 		server 10.0.1.123 iburst trust minpoll 0 maxpoll 0 xleave presend 9
> 		port 0

I would suggest that take off all of the cruft from that server command and
then if you want, add one at a time. Your system is saying that it cannot
reach the server, and it is probably because of the options (of course that
server might just not be working). Are you sure it is port 0 it wants to
addressed on to deliver time?)
I also assume that the port 0 was supposed to be part of the previous line.
and it is your email that shoved it onto its own line.

You have not told us what in the world that server is.



> 		driftfile /var/lib/chrony/chrony.drift
> 		makestep 10 3
> 		maxupdateskew 100.0
> 		maxdistance 10
> 		hwclockfile /etc/adjtime
> 		rtcsync
> 		local stratum 10
> 		keyfile /etc/chrony.keys
> 		leapsectz right/UTC
> 		logdir /var/log/chrony
> 		logchange 0.5
> 		mailonchange admin.time@xxxxxxxxxxx 1.0
> 		dumpdir /var/lib/chrony
> 		dumponexit
> 		sourcedir /run/chrony-dhcp
>
> where
>
> 	host 10.0.1.1
> 		1.1.0.10.in-addr.arpa domain name pointer edge.example.com.
>
> is a local chronyd server.

Then why do you have 10.0.1.123 in chrony.conf?

> In journal, I see repeating, ~ randomly-spaced
>
> 	...
> 	Oct 09 10:18:21 svr03.example.com chronyd[5922]: Forward time jump detected!
>
> 	Oct 09 10:18:21 svr03.example.com chronyd[5922]: Can't synchronise: no selectable sources
>
> 	Oct 09 10:18:24 svr03.example.com chronyd[5922]: Selected source 10.0.1.123
>
> 	Oct 09 10:43:36 svr03.example.com chronyd[5922]: Forward time jump detected!
> 	Oct 09 10:43:36 svr03.example.com chronyd[5922]: Can't synchronise: no selectable sources
> 	Oct 09 10:43:38 svr03.example.com chronyd[5922]: Selected source 10.0.1.123
> 	Oct 09 11:23:49 svr03.example.com chronyd[5922]: Forward time jump detected!
> 	Oct 09 11:23:49 svr03.example.com chronyd[5922]: Can't synchronise: no selectable sources
> 	Oct 09 11:23:52 svr03.example.com chronyd[5922]: Selected source 10.0.1.123
> 	Oct 09 12:18:30 svr03.example.com chronyd[5922]: Forward time jump detected!
> 	Oct 09 12:18:30 svr03.example.com chronyd[5922]: Can't synchronise: no selectable sources
> 	Oct 09 12:18:33 svr03.example.com chronyd[5922]: Selected source 10.0.1.123
> 	...
>
> it clearly selects a source
>
> 	chronyc sources
> 		MS Name/IP address         Stratum Poll Reach LastRx Last sample
> 		===============================================================================
> 		^* edge.example.com       2   0   377     5  -2286ns[-2245ns] +/-   14ms
>
> and is tracking
>
> 	chronyc tracking
> 		Reference ID    : AC1E0B64 (edge.example.com)
> 		Stratum         : 3
> 		Ref time (UTC)  : Fri Oct 09 19:25:08 2020
> 		System time     : 0.000000001 seconds slow of NTP time
> 		Last offset     : +0.000000040 seconds
> 		RMS offset      : 0.000017781 seconds
> 		Frequency       : 91408.953 ppm slow

That is essentially the maximum.

> 		Residual freq   : -0.000 ppm
> 		Skew            : 1.714 ppm
> 		Root delay      : 0.024624441 seconds
> 		Root dispersion : 0.002169367 seconds
> 		Update interval : 2.0 seconds
> 		Leap status     : Normal
>
> is that "Can't synchronise: no selectable sources" msg an actual problem, caused by my (mis)config, or a red-herring?

There is certainly something very wrong.

> --
> To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "unsubscribe" in the subject.
> For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "help" in the subject.
> Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.

--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.