Re: Silent Failure -- Enhancement Request
Bryan Christianson <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <[email protected]> |
You could monitor the Reach field of chronyc and check that it has a value of 377, raising an appropriate alarm for your system on failure. > On 19 Apr 2024, at 10:45, Chris Knox <Christopher.Knox-E0T7EY2UX4gpIyhaTEd/[email protected]> wrote: > > We recently moved a bunch of systems out of a data center and shut it down. Time sync was an overlooked item in the move. As a result, the time server was not reachable, but it did not become apparent until servers started drifting enough to create issues. Looking in the syslog of the various systems, the only entries I see are when chronyd could again hit the time server. Over the previous weeks, chronyd suffered in silence until we were able to establish a valid time server, at which point log entries came fast and furious because the time was more than .5 seconds out. Yet there was no message for all that time (several months) during which one server drifted out synch by more than 30 seconds. Is there a configuration in chrony.conf to complain when the time server is not reachable? If there is, why isn’t that the default behavior? > -- > Chris Bryan Christianson [email protected] -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]