Re: [chrony-users] Chrony IPv6 sources offline after resume - dispatcher script runs before IPv6 is up |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony IPv6 sources offline after resume - dispatcher script runs before IPv6 is up
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 16 Aug 2021 08:22:26 +0200
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1629094943; 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=a2vVrcXAJuaUkP8/h9ebiJdPpydG16zRf9hKyaOZMnE=; b=GUxe4NrAmHTm8gKKU4iIzaxbKH7rc//VuumndRsOC0tT3dDK6A8A5s5uRLGLEDXwa8fJig uA6DJWah+EMmX2qedgOnHApFTX+GsU8ZwoYCO+NQzQLAMbMz6q40OEGH/bT1Yde+Kvg1pQ 9ozyUD7g7DWG4O5OE5n1AD5d+6uKcSc=
On Thu, Aug 12, 2021 at 09:03:44PM +0300, Andrei Borzenkov wrote:
> The reason is - when ifup dispatcher script runs, IPv6 is not yet
> configured. Here are route entries
We had a bug report for this issue in Fedora [1]. I'd suggest to
submit an issue in the NetworkManager gitlab instance. I suspect the
fix is not easy and a new event might need to be specified for this
case.
As a workaround, we can consider forking in the dispatcher script and
running the chronyc command for second time after a short sleep, or
maybe check for addresses in the tentative state in a loop.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1811829
--
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.