| Re: [chrony-users] chrony configuration help (please) |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Tue, Aug 04, 2015 at 08:35:23PM +0200, Mauro Condarelli wrote:
> / # date -s '2025-01-07'
> Tue Jan 7 00:00:00 CET 2025
>
> Jan 7 00:00:00 ok-cash daemon.warn chronyd[494]: Forward time jump detected!
> Jan 7 00:00:00 ok-cash daemon.info chronyd[494]: Can't synchronise: no reachable sources
> Jan 7 00:02:55 ok-cash daemon.info chronyd[494]: Selected source 192.71.245.44
> Jan 7 00:02:55 ok-cash daemon.info chronyd[494]: Selected source 212.45.144.206
> Jan 7 00:02:55 ok-cash daemon.info chronyd[494]: Selected source 193.204.114.233
> Jan 7 00:02:56 ok-cash daemon.info chronyd[494]: Trimming RTC, error = -21.945 seconds
> Jan 7 00:03:37 ok-cash daemon.info chronyd[494]: Trimming RTC, error = -5.648 seconds
> Jan 7 00:04:18 ok-cash daemon.info chronyd[494]: Trimming RTC, error = -5.348 seconds
>
> As You see it takes about 3 min to resync... but date is not really corrected.
The "makestep 10 3" directive in your config allows chronyd to step
the clock only in the first three updates. If you set the clock at
some later point, chronyd will only slow down or speed up the clock
which will take forever to correct.
> I do not really understand these very large errors; shouldn't they decrease?
Yeah, RTC definitely shouldn't be gaining 5 second offset every
minute. If the problem is in setting the RTC, it could explain that.
--
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.