Bug#835222: needs multiple restarts until network is fully up

[Felipe Sateler]

Control: tags -1 moreinfo
Hi,

On 23 August 2016 at 13:22, Marc Haber <mh+debian-bugs at zugschlus.de> wrote:
> Package: systemd
> Version: 215-17+deb8u4
> Severity: minor
> File: systemd-networkd
>
> Hi,
>
> this is a monster. But relax. Severity: minor.
>
> I am doing virtualization on an AMD APU machine (pc-engines.ch APU2).
> The network setup is rather complex, with multiple physical
> interfaces, bridges and VLANs. systemd-networkd is unable to bring up
> this configuration in the first try most of the time. About once in
> ten tries, it works. In the other cases, multiple invocations of
> systemd-networkd restart are needed until the machine has its network
> fully initialized.

The notworking.txt file has this on all failed starts, and it is not
present in the working start nor the working.txt file:

Aug 23 16:20:33 prom systemd-networkd[XXX]: Event source
0x55ff6e8ec070 returned error, disabling: No buffer space available

So I suppose your config is simply too large and some queue is filling
up as systemd-networkd is taking too long to process it.
Unfortunately this message is very unhelpful (it was improved in
version 229[1]),
so it is hard to guess which queue it is.


> I will try to reproduce this in a VM, so that I can try whether this
> still happens with a more current systemd-networkd, but I am not sure
> whether this will work since this is probably a race or timing issue.

If the above error is important (and I think it is), then it might be
even easier to reach the error as the VM will likely be slower than
your real machine (and thus queue processing slower). It would be
great if you could try reproducing this in a VM.


[1] https://github.com/systemd/systemd/commit/0ced2b12891b87523eea06f1a88bb8d62b4e1e27
-- 

Saludos,
Felipe Sateler