[chrony-users] chronyd -q fails

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]

To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: [chrony-users] chronyd -q fails
From: Dennis Nelson <ddn@xxxxxxxxxxxxx>
Date: Fri, 15 Nov 2024 12:31:32 -0600
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s2048; t=1731695506; bh=yO9NQndkGNOOYa6gsoVFkuLOZYIK3G4LpcKpuv7j1rU=; h=From:Date:Subject:To:References:From:Subject:Reply-To; b=Pn7WZvAZZ1cySzKTBEuZF6rQoVTIsOnaOrG0boLG8zWait62FI9NMGgtLtDShhZWZc/305c4qVrjPqnN+Nd7rQCh9gu+Byi2tkhRJckmD1lSP5SeGeixY3GxOY4f7Nqp8L6MDr/9bFFFletEcL0bUfCu2ZMrvUPIpqN2s5lDGEOieusDfeIWLWAVdO/zHSSsReMuJG/vacSEK3hlW9zt391PV0yANDgt4QUv+gOGVd3hNxbBsC/equBEKjtZzH8W7w53IaObtPIV0wr+5Nd1h+vepyYHC5j7jUFTl9MR7xIwlsb+pQ1E10V0QdjKEW9iIlNm3v74vomGHKyOQjDncg==

Hello,

I have seen a number of cases where chronyd -q fails with "No suitable source for synchronisation" while the chronyd daemon starts and synchronizes without issue. Is there something different about the -q option that uses a different port or something different that causes chronyd -q to fail while the chronyd daemon starts and works without issue.

It is not something that happens everywhere I go, so I assume that it has something to do with firewall rules but I'd like to know what to look for to make it work.

Thanks,

Follow-Ups:
- Re: [chrony-users] chronyd -q fails
  - From: Miroslav Lichvar

Messages sorted by: [ date | thread ]
Next by Date: Re: [chrony-users] chronyd -q fails
Next by thread: Re: [chrony-users] chronyd -q fails

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/