[chrony-users] Frequency of requests to a source whether it is available again

[Kaelin Philippe SBB CFF FFS <philippe.kaelin@xxxxxx>]

Dear all

I have a question about the behaviour of the frequency of requests to a source whether it is available again.

We did some tests in the lab. In the configfile, we configured the following for polling:

 

server 10.124.219.170 iburst nts prefer minpoll 2 maxpoll 4 maxunreach 3

server 10.165.224.9 iburst nts prefer minpoll 2 maxpoll 4 maxunreach 3

server 10.165.230.167 iburst nts minpoll 2 maxpoll 4 maxunreach 3

 

After that we closed all NTS and NTP ports and from 15:00 UTC July 17 chrony recognised this relatively quickly. The query whether a source is available again increases exponentially (see log).

We want the fastest possible response time, even after an outage of 2 days. I reopened the ports today 20 July and waited for over an hour, but without success.

Is there an option to shorten or deactivate this so that he queries the sources at regular intervals (e.g. 5 minutes)?

 

Thank you for your help :)

Kind Regards

Philippe

 

Jul 17 15:00:24 ostp6-nts-poc-ngb chronyd[68517]: Can't synchronise: no selectable sources (3 unreachable sources)

Jul 17 15:00:36 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:00:38 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:00:40 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 15:01:09 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:01:11 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:01:12 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 15:01:57 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:01:59 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:02:01 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 15:03:18 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:03:20 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:03:22 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 15:05:43 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:05:46 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:05:47 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 15:10:18 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:10:20 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:10:21 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 15:19:12 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:19:14 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:19:16 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 15:36:42 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 15:36:45 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 15:36:48 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 16:11:10 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 16:11:15 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 16:11:16 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 17:19:51 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 17:19:53 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 17:19:57 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 17 19:36:43 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 17 19:36:47 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 17 19:36:48 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 18 00:10:11 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 18 00:10:13 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 18 00:10:16 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 18 09:16:39 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 18 09:16:40 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

Jul 18 09:16:45 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 19 03:29:20 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.224.9:4460 (10.165.224.9) timed out

Jul 19 03:29:21 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.165.230.167:4460 (10.165.230.167) timed out

Jul 19 03:29:21 ostp6-nts-poc-ngb chronyd[68517]: NTS-KE session with 10.124.219.170:4460 (10.124.219.170) timed out

C2 - Intern: Diese Informationen sind vertraulich zu behandeln und dürfen nur im geschäftlichen Kontext verwendet werden. Eine Weitergabe an Dritte ist nur in Abstimmung mit der SBB zulässig. // C2 – Interno: Queste informazioni devono essere trattate in modo confidenziale e possono essere utilizzate solo in ambito aziendale. La trasmissione a terzi è consentita solo previo accordo con le FFS. // C2 – Interne: Ces informations doivent être traitées de manière confidentielle et ne doivent être utilisées que dans le contexte des affaires. Un transfert à des tiers est permis uniquement sous réserve de l’accord des CFF. // C2 - Internal: - This information is to be treated as confidential and may only be used for business purposes. Disclosure to third parties is only permitted with the prior agreement of SBB.