Re: [chrony-users] Fallback clock on event "Can't synchronise: no reachable sources"

[Bill Unruh <unruh@xxxxxxxxxxxxxx>]

On Fri, 7 Feb 2014, Ulrich Schwesinger wrote:

> Hi,
>
> I am a regular chrony user and I have a question related to the behavior of 
> chrony in the case of the event: "Can't synchronise: no reachable sources".
> chrony rev.: 1.29
>
> I have a system with a write protected system partition and an NTP server 
> running within a local network. Sporadically, chrony reports the above 
> mentioned error.
> The error persists maybe within a time range of 20-30 seconds. Within that 
> time interval, the system time seems to diverge/drift by a couple of 10 
> milliseconds, which seems unreasonable large for me.

That is far tooo large. chrony will just let the clock freewheel.

> My questions are now:
> (a) What is chrony exactly doing upon the event "Can't synchronise: no 
> reachable sources". It does not seem to keep the current system time. Is it 
> falling back on hardware clock maybe?

It should not.

> (b) Or might something be wrong with the drift estimate, causing this large 
> divergence during the short time interval
> (c) Are there some files I could look at the trace back what's happening 
> within these time intervals?
>
> Thank you for your answers,
>
> Ulrich

--
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 |     unruh@xxxxxxxxxxxxxx
Canada V6T 1Z1     |      and Gravity       |  www.theory.physics.ubc.ca/

--
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.