| Re: [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 Sat, 27 Aug 2011, thomas.schmid@xxxxxxxxx wrote:
Hi all,
I run into the problem mentioned in the FAQ "10. Problems with isolated networks". We have the situation where the computer system in question might come up quite frequently with a large time offset (due to BIOS battery removal, or bad batteries etc) and network access is not available just at boot respectively at chrony startup time (so "initstepslew" can not help).
So why not delay chrony startup until network access IS available? Clearly
chrony trying to slew 45 years of offset is an exercise in futility. So that
fact that chrony is running while your system is way way off time is useless.
chrony needs a time source to sync you system to. Having absolutely none makes
running chrony during that time pointless. Either that or you could get a gps
receiver (eg the Sure receiver) which would give you ms accuracy right off the
bat.
What is the exact amount of time difference chrony still can handle ?
Not sure what you mean by this? Chrony should not care-- it will simply
attempt to slew the time. But far better is
When I tested this, I found that chronyd dies with a SIGABRT, and leaves no traces in syslog about what had happened. Is there a way to configure chrony to handle such a situation in a more benign way, ie leaving a last message ? Or chronyd being kept alive, so it could be questioned by chronyc about such a condition ?
It sure should not crash. That is clearly a bug in chrony. When did this crash
happen? When it finally found a time source? How far off was the system time
when it happened? Do you have logs from before that crach and during that
crash ( /var/log/chrony/measurements for example)
[Note: I hope this problem has not already been discussed to dead before, but I could not find an answer in the mailing list archive].
---
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.