AW: AW: [chrony-users] Chronyd aborts when system time differs too much from chrony's measurements

[<thomas.schmid@xxxxxxxxx>]

Hi Miroslav,

>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 have attached the backtrace, but have not found anything of interest in it
besides the SIGABRT.

>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. 
Oops, I am using "-r" and I am touching the BIOS clock manually.

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

Thomas

Attachment: chronyd_core_abort_20110829.tar.gz
Description: chronyd_core_abort_20110829.tar.gz