| Re: [chrony-users] chronyd -q fails |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] chronyd -q fails
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 18 Nov 2024 11:44:51 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1731926697; 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=tQ9o4rofDTxTUcjkwry3fuQR/asdbC+HrOWvcPhXVCg=; b=TL/H2FmvQgjOcTihD9QYPIzFSHsebT3P37mU4aP8FR8/W4ekgavDIUrZJV2HeNQ6EK6jRB G8RFAlwgjsQAfXtNreglVCcIFAxwqUy+zZNRNvOcmPiYHQ9XSiHSkq8oVTT24FdRErOJN5 Tj3iMnFM/5Ypto9GShatIRdOvqV25g4=
On Fri, Nov 15, 2024 at 12:31:32PM -0600, Dennis Nelson wrote:
> 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.
Maybe chronyd -q is started too early, when the network is not up yet?
There should be no difference in ports, but chronyd -q gives up if it
doesn't get a response to first 5 or 6 requests, while the daemon will
continue to poll the server as long as it's running.
--
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.