Re: [chrony-users] chrony configuration help (please)

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Mon, Aug 03, 2015 at 10:56:51PM +0200, Mauro Condarelli wrote:
> Absolute precision is not a requirement, I can tolerate errors of several seconds, but I cannot leave clocks to drift and rely on manual resynchronization.
> 
> My  current /etc/chrony.conf is:
> ===============================
> server 0.it.pool.ntp.org
> server 1.it.pool.ntp.org
> server 2.pool.ntp.org
> server 3.pool.ntp.org
> 
> logdir /var/log/chrony
> log statistics measurements tracking
> driftfile /var/lib/chrony/drift
> keyfile /etc/chrony.keys
> generatecommandkey
> makestep 10 3
> maxupdateskew 100.0
> dumponexit
> dumpdir /var/lib/chrony
> rtconutc
> rtcautotrim 1
> rtcfile /var/lib/chrony/rtc
> ===============================
> 
> This, however, is far from being optimal for (at least) two reasons
> 
> 1. If, for any reason (e.g.: battery disconnection), the RTC loses the right time Date is severely (several years) in the past for minutes, even if the system is connected to the Internet.

You can speed up the initial synchronization by adding the iburst
option to the server lines, or use the initstepslew directive. You
may also want to start chronyd with the -s option so it sets the
system clock from RTC with compensated drift.

> 2. In the above event, after several minutes, chrony announces it is going to step by several million seconds (as expected); shortly thereafter system dies... somewhat; i.e.: serial console and ssh are completely unresponsive, but "ping" gets an answer. Nothing is logged.

Hm, that's odd. Can you reproduce the problem by stepping the clock
manually with the date command, e.g. date -s '+ 1000000 sec' ?

-- 
Miroslav Lichvar

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