| Re: [chrony-users] chrony configuration help (please) |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Wed, Aug 05, 2015 at 09:55:29AM +0200, Mauro Condarelli wrote:
> Il 05/08/2015 03:12, Bill Unruh ha scritto:
> >Maybe there is something which puts the system to sleep if it is inactive to a
> >long time. since a million seconds is certainly a long time, that thing could
> >decide you have been inactive and puts everything to sleep. Then when things
> >start to happen again, it wakes up
> This does not really look true: kernel (at least lower levels) seems active (ping works and serial console input char are correctly buffered; also ssh connection is kept alive).
> I was doing absolutely nothing on target that could "revive" it.
>
> It seems like "Trimming RTC" takes a long time to execute when error is large; is that possible?
It could be. The "Forward time jump detected!" means the clock has
jumped without chronyd knowing, as it would if the system call which
sets the RTC was blocked for more than 10 seconds.
The messages about trimming RTC every minute or so suggest there is
something wrong with the RTC in any case.
> Can You suggest what I should try?
> I'm currently out of ideas.
Try it again without the rtcfile directive in chrony.conf. That will
disable all RTC reading and trimming. If that works, it could be a
problem with the RTC kernel driver.
--
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.