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:
> > > > [Unit]
> > > > Description=A remote mail retrieval and forwarding utility
> > > > After=network-online.target opensmtpd.service unbound.service
> > > > Requires=opensmtpd.service unbound.service
> ...
> > In case of my fetchmail setup the culprit is unbound. At the startup
> > of unbound it takes some time to exchange keys and so on.
> 
> 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.
> ...
> > > However avahi-autoipd should be started concurrently
> > > with network configuration to assign link-local address in the case of
> > > failure.
> > 
> > In a different thread - it was about IPv6 which has mutated
> > slightly - several users claimed that the avahi-autoip is useful for
> > their business.
> 
> I mean IPv4 link local addresses 169.254.x.y. My impression is that
> avahi-autoipd was created for the cases when there is no point to setup
> centralized DHCP server. On the other hand I agree that a router (and so
> DHCP out of the box) is more wide spread configuration than connecting a
> couple of devices directly or through a switch.

I think so, too. 

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.

Reply via email to