| 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: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 2 May 2024 15:12:16 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1714655540; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=yIzWr4cUrfWkc5h73EUVmBoPIrAujpN0IXDI/EcrOs0=; b=en7lYHoP9eGSKoA+Y0/s2K3ImJ/SKThFVYWKndZpUXXdwHEzklsL0i4NQHJqNy1pd8aPvX FCgMHsF0ub01DT1MhFlXKpSDGa8VgbVVJ93bZxyl40BPJw2Oh1ZgAS2/QnAtLL0o1FssX2 gjW90/lq9IEDUJyRgZdbaQlk4VzxWjc=
On Mon, Apr 22, 2024 at 03:54:50PM +0000, Chris Knox wrote:
> That sounds to me like a vast improvement. According to Syslog documentation, Facility 12 is reserved for the NTP subsystem -- so Chrony has its own Syslog facility to work with. A Warning (Severity 4) on startup to Syslog about unreachable time sources would help, followed by an Error (Severity 3) if no time sources can be reached after some reasonable interval. If no time source is available for some extended time (Days? Weeks?), then there is a case to be made for logging it as Critical (Severity 2), which should be enough to attract attention.
In some configurations it can be expected. With the local directive it
can work as an NTP server even if it has no sources.
Anyway, with the latest code in git there should be one info message
logged soon after start (after first source has 8 polls) if the
selection fails.
This is not intended to replace a proper monitoring system.
--
Miroslav Lichvar
--
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.