| AW: 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
]
- To: <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: AW: AW: [chrony-users] Chronyd aborts when system time differs too much from chrony's measurements
- From: <thomas.schmid@xxxxxxxxx>
- Date: Wed, 31 Aug 2011 01:15:03 +0000
- Accept-language: de-CH, en-US
- Thread-index: AQHMZNfYruuXH1l/z0Gzkl/J+GmVDJUw96zv///51ICAAN19F4AB3paAgAJ/CbY=
- Thread-topic: AW: [chrony-users] Chronyd aborts when system time differs too much from chrony's measurements
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.
>.... 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.
Can you do something about that ?
Regards,
Thoma
---
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.