| Re: [chrony-users] Silent Failure -- Enhancement Request |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Silent Failure -- Enhancement Request
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Fri, 19 Apr 2024 11:27:52 +1200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smtpservice.net; i=@smtpservice.net; q=dns/txt; s=a1-4; t=1713482891; h=feedback-id : x-smtpcorp-track : date : message-id : to : subject : from : reply-to : sender : list-unsubscribe; bh=gm3nEH22mutXI3NZAx3oIMI7JFuYzsEB4NtD7bNqny0=; b=Pe1mzOd3i8POcIXjETWz1d3KGVvBTdYzHleyu0pKVa94VXkiFrhy5O/pH6WqwH+VaNexd BsElsUcTg718JKjzo2YhFiDoZ9IWuDgJklbJrLa+i4FhCxZq0dNRKKSbieM7k+FOQi40YLZ JFDag2SKkstA7EFsIqpG0e1Y/Itexn+LRL5en9xdQKdt95+MYvx94/dmJc10TKwHmSzF0Mr DE1uKUDeMsFSThstKPDRWQXuRikJJhcuGyBTubsK14ww8423VM5oXXGO9PFNgFkgMnQjJ9R WrOljKNDqFKZ7zjTZtLBWq6vbVF0G6yLyEKaGm8hzaXQlOeAh+ghgnF6nQjA==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whatroute.net; i=@whatroute.net; q=dns/txt; s=s149811; t=1713482891; h=from : subject : to : message-id : date; bh=gm3nEH22mutXI3NZAx3oIMI7JFuYzsEB4NtD7bNqny0=; b=OY5dejgW72THush88jzyZVDeXNjxZ1iFBWbvFKd2uCAXiF5fZVj+LWkS5CbcJZ7X+z+hQ dj0Tbci2kAKI7/DBITwp9Fr1kCiv0cBT9xnH2eCTLVkjuxO7nPI7mfrJCHo3Io3LIBJhpBO tU6yBYFTaFKqCa81TWjbBVimF29Z8nX2PQJLCjBB23FwN9aGXTu93SHRgVhxTPPYqaWF5xo 5FUW4w/4bMS42XgosEpSpKp4RQfDCm/ZB1i+4se0MXJ/t6FVBDhTA9vkC3r/pqKtF5oqRMm E0bwFqxBjysLLwZeQ/ujqVjBRp+zeIyHCbhMhgawBRgd3tc5Qw46y2hi1lHg==
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@xxxxxxxxxxxxxxxx> 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
bryan@xxxxxxxxxxxxx
--
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.