| RE: [chrony-users] Silent Failure -- Enhancement Request |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] Silent Failure -- Enhancement Request
- From: Chris Knox <Christopher.Knox@xxxxxxxxxxxxxxxx>
- Date: Fri, 19 Apr 2024 14:40:55 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=choicehotels.com; dmarc=pass action=none header.from=choicehotels.com; dkim=pass header.d=choicehotels.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=YbYUzUwY+XHbdAb4IjPY08zbyir+FBuZ9KgdK6pgOqc=; b=k61f0mmzGU1Rz2eSo5t9868Oh6NuGXNuXB2u62O8xAnw5B+JG/7rNLhr2bK1rm4v+XB/eVr3vhLgZMzan9m9XL0hAUpkGWE7ieIm4srKmgy7T8kesGfip02mxfcr9gBiK/xK+m2y0IVfsg7I69SouHMvie3zN/fMJmfNFZdg2hs3o7lEPXhKc7WZlmwwkHpMx8fpNGf//Q+1O8R6Rk6PbyY0d24Yz93BoS0lmC4jEG1OlPxrQZcxVvonNRV/vZl6DPBNPKF+5JjlHnsvNX5pZP4uWPdnQ3wl+fa7Gisir6ELw4qcmX0RjIcQkHerHZOsoy+dAXzJ7KX5EvHaxJmoxg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dZXIsCq93Qyap5LobwL8H3UFBX/F9bUenrdC1MWnjLzSRbSSum49IyhPR/3HnTqiusgwetT0F3UwzDewALqXxsxXu5T4R12yYDkKrYf91BqA9pDH0n88A9Xls5YKhN20LU66ygzusMxzjMUHAvyDIKEAt5S322m/mk8j+6GfIaGtK9e/ntETnHFALnr5m3HLrMFv1dnG0EUOAD27FkSiAQtZuDVEZSTyqyybvk7ymYHv2a6FHsKpPPSxQQK1qXecZNtxPNbscjgEXw8Up0xWAGwmxM603Nqhnxy8/4aqQ1dJU6ZFGYJhXkaDvJZ6hZh/ibD3Dmho/OD9/EVcDjBhsA==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=choicehotels.com;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=choicehotels.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=YbYUzUwY+XHbdAb4IjPY08zbyir+FBuZ9KgdK6pgOqc=; b=mh+Snwkb/jcNEpRBkYjqSSXIP1VgRvyAwBg89cKejhwYCpFg62GGSaiGwRt+Mvqb8rT4mC7aXyxtE8IKMKywwRywuLvMi3eVnmFYG4OtjE/Ri6E+G00EOw3omM7KOJ0HLfsM5I4H9lGuHOtmusea8LElGVVwWUz2HXh/C0RzgWA=
- Thread-index: AdqR4Itg/wSDCwNeSAOp8ZpWeVYsVgAB30AAAB8uyBA=
- Thread-topic: [chrony-users] Silent Failure -- Enhancement Request
Bryah, thanks for the answer. Yes, now that we have the scars, we're monitoring chronyd's health carefully. But my question goes a bit beyond that. If chronyd is configured and running, that implies that the owner of the system wants the time to be correct. If the configured time source is not reachable, it seems at least as important as chronyd being out by a half-second and worth logging to syslog where someone who is not a time synchronization expert will notice something being amiss. In effect, chronyd will tell me if it has a figurative hangnail, but will suffer in silence if it is starving.
I would suggest the Chrony authors add a default configuration to call for help if the time source is unreachable. Is this an appropriate venue to ask for that enhancement?
--
Chris Knox
IT Infrastructure Engineer
tel 1.602.308.5438
18615 N. Claret Dr., Scottsdale, AZ 85255
Christopher.Knox@xxxxxxxxxxxxxxxx
-----Original Message-----
From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
Sent: Thursday, April 18, 2024 4:28 PM
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] Silent Failure -- Enhancement Request
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.