| Re: [chrony-users] Problem when removing all sources |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Problem when removing all sources
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 21 Nov 2023 12:51:48 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1700567511; 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=5yuB50SKiOi1QauXSq56lIo1uxXARWsNTAn/hHmcVVU=; b=GwRwkC6aNIz5PMo28JDDlX5keM7oUjai+GRgvtab84/3DHE8T8u+jYNuw7S29W71uHva3W XIPaheKx5LNwSJPgE1J3RaGNe33Q7D4it0kxcbToObXpfj1AafeQzB6b1pS34A4bacyCNO zw5ZxiJ/1/kykaRgLuDGd7RKwdvli1A=
On Mon, Nov 20, 2023 at 04:17:47PM +0100, Miroslav Lichvar wrote:
> On Mon, Nov 20, 2023 at 11:14:00AM +0100, Thomas Lange wrote:
> > <chronyc reload sources>
> >
> > 2023-11-19T17:43:20Z Removed source 103.242.68.69
> > 2023-11-19T17:43:20Z Removed source 162.159.200.123
> > 2023-11-19T17:43:20Z Removed source 194.58.202.148
> > 2023-11-19T17:43:20Z Selected source 194.58.206.20
> > 2023-11-19T17:43:20Z Removed source 194.58.206.20
> > 2023-11-19T17:43:20Z Removed source 217.75.106.216
> > 2023-11-19T17:43:20Z Removed source 91.209.0.17
> >
> > <Missing "Can't synchronise: no selectable sources" >
>
> It depends on the order of removed sources and the reselection that
> can happen.
>
> The message is logged only when a source is already selected and
> newly executed source selection doesn't find a selectable source.
> In your example the last selected source is 194.58.206.20. It is
> removed, i.e. nothing is selected, and with the two remaining sources
> there is no successful selection.
The issue actually was in the removal of the source. If it was
reselected due to becoming offline, the log message was logged. If it
was kept selected even as offline (due to other sources not being
better), it would not be logged.
The latest development code now has a fix to make it consistent.
--
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.