Re: chronyd -q fails
Miroslav Lichvar <[email protected]> Mon, 18 Nov 2024 11:44:51 +0100
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <Zzsao8oPIc8Jl1Pj@localhost> |
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-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]