| Re: AW: [chrony-users] Chronyd aborts when system time differs too much from chrony's measurements |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Sun, Aug 28, 2011 at 06:43:38AM +0000, thomas.schmid@xxxxxxxxx wrote:
> I have attached the logs from chrony when it crashed this morning:
> - I let chronyd run the whole night and do its measurements, then stopped chronyd,
> - set the system time back by 1h and wrote this new system time to the BIOS clock
> using hwclock. This to simulate a time change by battery failing, as I have no
> physical access to the test system now.
The SIGABRT signal indicates an assert() has failed, but there is no
such message in the system log. Can you please try that again with
chronyd running in the foreground (-d option) or make a backtrace from
coredump?
I see there are some *.dat files in the log directory, did you start
chrony with the -r option after reboot? It's meant to be used only
when the the system clock was not touched in any way since the dump
was made. I suspect one of the sourcestats asserts which check for
samples from future would fail here. Of course, chronyd should just
ignore an invalid dump and not crash.
--
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.