RE: Silent Failure -- Enhancement Request

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.

Sev 3 or better errors showing up repeatedly in the Syslog should be enough to wake up even the dumbest monitoring systems.  

Thanks for considering this issue.  Hopefully this experience can improve the tool.


--
Chris Knox

-----Original Message-----
From: Miroslav Lichvar <[email protected]> 
Sent: Sunday, April 21, 2024 11:30 PM
To: [email protected]
Subject: Re: [chrony-users] Silent Failure -- Enhancement Request

On Thu, Apr 18, 2024 at 10:45:10PM +0000, Chris Knox wrote:
> 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?

chronyd logs "Can't synchronise: no selectable sources" when all
sources become unreachable. It doesn't log that if they were never
reachable. Maybe it should do that after 8 polls after start.

-- 
Miroslav Lichvar


-- 
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]


-- 
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]