Il 02/08/21 02:08, Andrei Borzenkov ha scritto:
On 01.08.2021 21:57, Carlos E. R. wrote:
On 01/08/2021 20.52, Andrei Borzenkov wrote:
On 01.08.2021 21:46, Marco Calistri wrote:
Il 01/08/21 15:30, Andrei Borzenkov ha scritto:
On 01.08.2021 21:22, Marco Calistri wrote: ...
> chronyc activity marco@localhost:~> chronyc activity 200 OK 0 sources online 6 sources offline 0 sources doing burst (return to online) 0 sources doing burst (return to offline) 0 sources with unknown address ...
Chronyc is tool to control chronyd just like ntpdc is tool to control ntpd.
Looking here after resume, interesting is that chronyd onlined some - but not all - servers. Two of them are IPv6 so it is possibly related to delay in IPv6 address configuration. Two of them are IPv4 so I do not really have explanation so far.
P.S. and yes, I of course have
chronyd[12089]: Forward time jump detected!
in logs after resume. Which explains zeroes in output shown originally. ---<SNIP>---
This below is the solution to avoid loosing the sync of chrony during st/by and resumes: Explanation: The makestep directive can be used to allow chronyd to step the clock. For example, if chrony.conf had makestep 1 3 the clock would be stepped in the first three updates if its offset was larger than one second. Normally, it’s recommended to allow the step only in the first few updates, but in some cases (e.g. a computer without an RTC or virtual machine which can be suspended and resumed with an incorrect time) it may be necessary to allow the step on any clock update. The example above would change to makestep 1 -1 https://chrony.tuxfamily.org/faq.html#_is_code_chronyd_code_allowed_to_step_... Best regards! -- Marco Calistri Build: openSUSE Tumbleweed 20210730 Kernel:5.13.4-1-default Desktop: XFCE (4.16.0)