Am Fri, Feb 24, 2023 at 07:41:26PM +0100 schrieb Christoph Brinkhaus: I reply to myself thanking Max.
> Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin: > > On 22/02/2023 23:45, Christoph Brinkhaus wrote: > > > Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin: > > > > On 22/02/2023 01:26, Christoph Brinkhaus wrote: [snip] > > I have no experience with unbound and I am not sure at which moment it > > notifies systemd that the service is ready. However I have found a recent > > bug > > https://github.com/NLnetLabs/unbound/issues/773 > > "When used with systemd-networkd, unbound does not start until > > systemd-networkd-wait-online.service times out" > > > > Perhaps the package in Debian has an older version of the unbound.service > > file and so is not affected. > > > Hi Max, > > I have observed lines below in journald: > > Feb 22 15:41:44 lenovo systemd[1]: Reached target Network is Online. > Feb 22 15:41:44 lenovo systemd[1]: Failed to start Wait for Network to be > Configured. > Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: > Failed with result 'exit-code'. > Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: Main > process exited, code=exited, status=1/FAILURE > Feb 22 15:41:44 lenovo systemd-networkd-wait-online[362]: Event loop failed: > Connection timed out > Feb 22 15:41:25 lenovo systemd[1]: anacron.service: Succeeded. > Feb 22 15:41:25 lenovo anacron[3261]: Normal exit (0 jobs run) > Feb 22 15:41:25 lenovo anacron[3261]: Anacron 2.3 started on 2023-02-22 > Feb 22 15:41:25 lenovo systemd[1]: Started Run anacron jobs. > > This looks related, thank you very much! > I will have a look at the link. Dear Max, the method descriped in the link above helped to fix the issue. Now there are no messages reported by journald as above. Thank you very much for the kind help! [snip] Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
