On Tue, 05 Apr 2022 18:48:19 +0200 Lupe Christoph <l...@lupe-christoph.de>
wrote:
This is on a server that has gone through many Debian releases. We
have not noticed until recently that ifupdown is deprecated. I started
converting from ifupdown to Netplan first on my home machines (Ubuntu
21.10), then worked on the server I'm sending this bug report from
(Debian 11). I'm sorry, but I did not yet try to see if the same is
happening on the two Ubuntu machines.
When I first rebooted the machine to see if the new configuration
was being stared OK (I had left out a Netplan configuration for lo,
noticing that lo was configured by default), there was a significant
delay. I later found out that it was exactly two minutes long.
systemd-analyze blame pointed to systemd-networkd-wait-online.service:
2min 363ms systemd-networkd-wait-online.service
I tried ignoring unimportant interfaces, but no dice. So I ran an strace
on /lib/systemd/systemd-networkd-wait-online (attached). I failed to
understand what is really going on, but the program configures a epoll
instance. After some successful use of that something fails to happen
Hi and sorry for the late reply!
There have been some difficulties in getting the
"systemd-networkd-wait-online.service"
working as expected, using Netplan. Slight changes in behavior in upstream
systemd
didn't help with Netplan catching up to it.
I think this recent upstream work should actually improve the situation, and I
hope to
get it landed in Debian soon:
https://github.com/canonical/netplan/pull/456
Cheers,
Lukas
