> I suspected that this patch
https://github.com/systemd/systemd/pull/16982 solved the issue.
can you explain *why* you suspect that fixes your problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
To confirm the focal fossa bug, I booted the server using the ubuntu
focal fossa live cd and applied the same configuration via netplan. Some
interfaces became failed/degraded as here
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/comments/13
--
You received this bug notification
Hi,
I booted the server using the ubuntu groovy live cd and applied the same
configuration via netplan. All interfaces became up.
I suspected that this patch
https://github.com/systemd/systemd/pull/16982 solved the issue. Can you
port this patch to focal fossa?
Thanks
networkctl -a
IDX LINK
I just tested that exact configuration and had no failures, so the
problem is something specific to your system; you should open a new bug
or ask for debugging help at askubuntu.com.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu Focal)
See the output of
networkctl -a
below after 11h uptime and see my configs attached
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 etherroutableconfigured
3 eth1 etherno-carrier configuring
4 eth2 ether
> Maybe this script can help to debug:
oh my, no.
please just attach the systemd-networkd config from your failing server.
If you are using netplan (looks like you are from your ansible config)
please include all files in /etc/netplan/ as well.
** Changed in: systemd (Ubuntu)
Status: Fix
@fabceolin your zip shows you have no systemd-networkd config files at
all
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1912331
Title:
Many interfaces lead to "kernel
I have 4 servers with Ubuntu 20.04.2 with more than 5 physical ethernets
interfaces each (one of then has 18 ethernets) and I had the problem
with 2 of them.
I can give you access to one of the servers with bug if needed. It's not
in production yet and I can cleanup everything after debug.
I
FWIW, I tried reproducing this artificially by running 200 Kubernetes
Pods on a freshly installed Focal and the issue did not occur.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu Focal)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1912331
Title:
Many interfaces lead to "kernel
Increasing the ReceiveBuffer=128M or ReceiveBuffer=512M didn't solve the
problem for me.
I'm interested to systemd patched backported to focal too.
See my config files.
** Attachment added: "config files"
https://bugs.launchpad.net/systemd/+bug/1912331/+attachment/5482905/+files/config.zip
You have systemd-networkd managing only a single interface, ens3.
Whatever your problem is, it's not at all the upstream bug you linked.
** Changed in: systemd (Ubuntu Focal)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
** Attachment added: "1912331-config-files.zip"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/+attachment/5466762/+files/1912331-config-files.zip
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
all your files in the directories:
/etc/systemd/network
/run/systemd/network
/lib/systemd/network
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1912331
Title:
Many
Where would I find those files? systemd-networkd is not something I have
consciously installed or configured, it just came with Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
please attach the systemd-networkd config file(s) so i can reproduce the
failure
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1912331
Title:
Many interfaces lead to
I don't completely understand it myself.
I have a Focal system with k3s installed and about 70 pods (about 150
containers) and about 70 veth devices.
In /lib/systemd/system/systemd-networkd.socket under "[Socket]" I have
set "ReceiveBuffer=128M".
Maybe that "128M" isn't enough but I can't add
> Can this be backported to Focal?
If I'm understanding the upstream bug correctly, this only affects those
using a really large number of interfaces and/or vlans and/or bridges on
a single system, and in that situation this can be worked around just by
increasing the socket receive buffer size
** Changed in: systemd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1912331
Title:
Many interfaces lead to "kernel receive buffer
** Bug watch added: github.com/systemd/systemd/issues #14417
https://github.com/systemd/systemd/issues/14417
** Also affects: systemd via
https://github.com/systemd/systemd/issues/14417
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Groovy)
Status: New => Fix Released
** Changed in: systemd (Ubuntu)
Status: New
21 matches
Mail list logo
