[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
> 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. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Invalid Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Invalid Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableconfigured 3 eth1 etherno-carrier configuring 4 eth2 etherno-carrier configuring 5 eth3 etherno-carrier configuring 6 eth4 etherno-carrier configuring 7 eth5 etherno-carrier configuring 8 br0bridge no-carrier configured 9 br1bridge no-carrier configured 10 br2bridge no-carrier configured 11 br3bridge no-carrier configured 12 br4bridge no-carrier configured 13 br4.8 vlan no-carrier configured 14 br4.4 vlan no-carrier configured 15 br4.7 vlan no-carrier configured 16 br4.2 vlan no-carrier configured 17 br4.9 vlan no-carrier configured 18 br4.14 vlan no-carrier configured 19 br4.3 vlan no-carrier configured 20 br4.17 vlan no-carrier configured 21 br4.0 vlan no-carrier configured 22 br4.12 vlan no-carrier configured 23 br4.10 vlan no-carrier configured 24 br4.5 vlan no-carrier configured 25 br4.6 vlan no-carrier configured 26 br4.16 vlan no-carrier configured 27 br4.11 vlan no-carrier configured 28 br4.13 vlan no-carrier configured 29 br4.15 vlan no-carrier configured 30 br4.1 vlan no-carrier configured 31 br3.5 vlan no-carrier configured 32 br3.10 vlan no-carrier configured 33 br3.4 vlan no-carrier configured 34 br3.1 vlan no-carrier configured 35 br3.0 vlan no-carrier configured 36 br3.6 vlan no-carrier configured 37 br3.16 vlan no-carrier configured 38 br3.11 vlan no-carrier configured 39 br3.12 vlan no-carrier configured 40 br3.14 vlan no-carrier configured 41 br3.8 vlan no-carrier configured 42 br3.15 vlan no-carrier configured 43 br3.2 vlan no-carrier configured 44 br3.17 vlan no-carrier configured 45 br3.3 vlan no-carrier configured 46 br3.7 vlan no-carrier configured 47 br3.9 vlan no-carrier configured 48 br3.13 vlan no-carrier configured 49 br2.6 vlan no-carrier configured 50 br2.3 vlan no-carrier configured 51 br2.16 vlan no-carrier configured 52 br2.17 vlan no-carrier configured 53 br2.8 vlan no-carrier configured 54 br2.15 vlan no-carrier configured 55 br2.1 vlan no-carrier configured 56 br2.2 vlan no-carrier configured 57 br2.0 vlan no-carrier configured 58 br2.10 vlan no-carrier configured 59 br2.13 vlan no-carrier configured 60 br2.11 vlan no-carrier configured 61 br2.5 vlan no-carrier configured 62 br2.9 vlan no-carrier configured 63 br2.12 vlan no-carrier configured 64 br2.7 vlan no-carrier configured 65 br2.14 vlan no-carrier configured 66 br2.4 vlan no-carrier configured 67 br1.13 vlan no-carrier configured 68 br1.16 vlan no-carrier configured 69 br1.3 vlan no-carrier configured 70 br1.0 vlan no-carrier configured 71 br1.17 vlan no-carrier configured 72 br1.14 vlan no-carrier configured 73 br1.2 vlan no-carrier configured 74 br1.7 vlan no-carrier configured 75 br1.1 vlan no-carrier configured 76 br1.5 vlan no-carrier configured 77 br1.9 vlan no-carrier configured 78 br1.4 vlan no-carrier configured 79 br1.11 vlan no-carrier configured 80 br1.12 vlan no-carrier configured 81 br1.15 vlan no-carrier configured 82 br1.6 vlan no-carrier configured 83 br1.8 vlan no-carrier configured 84 br1.10 vlan no-carrier configured 85 br0.5 vlan no-carrier configured 86 br0.13 vlan no-carrier configured 87 br0.12 vlan no-carrier configured 88 br0.11 vlan no-carrier configured 89 br0.0 vlan no-carrier configured 90 br0.1 vlan no-carrier configured 91 br0.15 vlan no-carrier configured 92 br0.3 vlan no-carrier configured 93 br0.14 vlan no-carrier configured 94 br0.4 vlan no-carrier configured 95 br0.7 vlan no-carrier configured 96 br0.6 vlan no-carrier configured 97 br0.2 vlan no-carrier configured 98 br0.9 vlan no-carrier configured 99 br0.10 vlan no-carrier configured 100 br0.16 vlan no-carrier configured 101 br0.17 vlan no-carrier configured 102 br0.8 vlan no-carrier configured 102 links listed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Groovy) Status: Incomplete => Invalid -- 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Invalid Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 etherno-carrier configuring 5 eth3 etherno-carrier configuring 6 eth4 etherno-carrier configuring 7 eth5 etherno-carrier configuring 8 br0bridge off failed 9 br1bridge no-carrier configured 10 br2bridge no-carrier configured 11 br3bridge no-carrier configured 12 br4bridge off failed 13 br2.14 vlan no-carrier configured 14 br2.5 vlan no-carrier configured 15 br2.4 vlan no-carrier configured 16 br2.8 vlan no-carrier configured 17 br2.10 vlan no-carrier configured 18 br2.13 vlan no-carrier configured 19 br2.2 vlan no-carrier configured 20 br2.15 vlan no-carrier configured 21 br2.7 vlan no-carrier configured 22 br2.11 vlan no-carrier configured 23 br2.12 vlan no-carrier configured 24 br2.9 vlan no-carrier configured 25 br2.3 vlan no-carrier configured 26 br2.17 vlan no-carrier configured 27 br2.6 vlan no-carrier configured 28 br2.16 vlan no-carrier configured 29 br2.0 vlan no-carrier configured 30 br2.1 vlan no-carrier configured 31 br3.7 vlan no-carrier configured 32 br3.0 vlan no-carrier configured 33 br3.11 vlan no-carrier configured 34 br3.1 vlan no-carrier configured 35 br3.9 vlan no-carrier configured 36 br3.3 vlan no-carrier configured 37 br3.13 vlan no-carrier configured 38 br3.15 vlan no-carrier configured 39 br3.8 vlan no-carrier configured 40 br3.6 vlan no-carrier configured 41 br3.17 vlan no-carrier configured 42 br3.10 vlan no-carrier configured 43 br3.2 vlan no-carrier configured 44 br3.12 vlan no-carrier configured 45 br3.14 vlan no-carrier configured 46 br3.5 vlan no-carrier configured 47 br3.16 vlan no-carrier configured 48 br3.4 vlan no-carrier configured 49 br1.5 vlan no-carrier configured 50 br1.1 vlan no-carrier configured 51 br1.8 vlan no-carrier configured 52 br1.6 vlan no-carrier configured 53 br1.14 vlan no-carrier configured 54 br1.16 vlan no-carrier configured 55 br1.10 vlan no-carrier configured 56 br1.0 vlan no-carrier configured 57 br1.3 vlan no-carrier configured 58 br1.15 vlan no-carrier configured 59 br1.11 vlan no-carrier configured 60 br1.4 vlan no-carrier configured 61 br1.13 vlan no-carrier configured 62 br1.17 vlan no-carrier configured 63 br1.7 vlan no-carrier configured 64 br1.2 vlan no-carrier configured 65 br1.9 vlan no-carrier configured 66 br1.12 vlan no-carrier configured 67 br4.16 vlan no-carrier configured 68 br4.12 vlan no-carrier configured 69 br4.14 vlan no-carrier configured 70 br4.11 vlan no-carrier configured 71 br4.5 vlan no-carrier configured 72 br4.6 vlan no-carrier configured 73 br4.3 vlan no-carrier failed 74 br4.7 vlan no-carrier failed 75 br4.17 vlan no-carrier failed 76 br4.8 vlan no-carrier failed 77 br4.4 vlan no-carrier failed 78 br4.10 vlan no-carrier failed 79 br4.13 vlan no-carrier failed 80 br4.15 vlan no-carrier failed 81 br4.1 vlan no-carrier failed 82 br4.9 vlan no-carrier failed 83 br4.0 vlan no-carrier failed 84 br4.2 vlan no-carrier failed 85 br0.14 vlan no-carrier failed 86 br0.0 vlan no-carrier failed 87 br0.13 vlan no-carrier failed 88 br0.2 vlan no-carrier failed 89 br0.3 vlan no-carrier failed 90 br0.7 vlan no-carrier failed 91 br0.4 vlan no-carrier failed 92 br0.17 vlan no-carrier failed 93 br0.5 vlan no-carrier failed 94 br0.6 vlan no-carrier failed 95 br0.8 vlan no-carrier failed 96 br0.9 vlan no-carrier failed 97 br0.11 vlan no-carrier failed 98 br0.10 vlan no-carrier failed 99 br0.1 vlan no-carrier failed 100 br0.16 vlan no-carrier failed 101 br0.15 vlan no-carrier failed 102 br0.12
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
> 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 Released => Incomplete ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Groovy) Status: Fix Released => Incomplete -- 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
@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 receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 tried to emulate the problem using KVM. I saw errors too (apparently non directly related with this issue) when use a lot of interfaces with bridges and vlans. Maybe this script can help to debug: wget https://releases.ubuntu.com/20.04/ubuntu-20.04.2-live-server- amd64.iso qemu-img create -f qcow2 disk1.qcow2 20G sudo -E kvm -m 4096 -netdev user,id=user.0 -device e1000,netdev=user.0 -device e1000,id=n1,mac=00:e0:4c:f6:02:3d -net tap,script=no,id=n1 -device e1000,id=n2,mac=00:e0:4c:f6:03:3d -net tap,id=n2 -device e1000,id=n3,mac=00:e0:4c:f6:04:3d -net tap,id=n3 -device e1000,id=n4,mac=00:e0:4c:f6:05:3d -net tap,id=n4 -device e1000,id=n5,mac=00:e0:4c:f6:06:3d -net tap,id=n5 -device e1000,id=n6,mac=00:e0:4c:f6:07:3d -net tap,id=n6 -device e1000,id=n7,mac=00:e0:4c:f6:08:3d -net tap,id=n7 -device e1000,id=n8,mac=00:e0:4c:f6:09:3d -net tap,id=n8 -device e1000,id=n9,mac=00:e0:4c:f6:10:3d -net tap,id=n9 -device e1000,id=n10,mac=00:e0:4c:f6:11:3d -net tap,id=n10 -device e1000,id=n11,mac=00:e0:4c:f6:12:3d -net tap,id=n11 -device e1000,id=n12,mac=00:e0:4c:f6:13:3d -net tap,id=n12 -device e1000,id=n13,mac=00:e0:4c:f6:14:3d -net tap,id=n13 -device e1000,id=n14,mac=00:e0:4c:f6:15:3d -net tap,id=n14 -device e1000,id=n15,mac=00:e0:4c:f6:16:3d -net tap,id=n15 -device e1000,id=n16,mac=00:e0:4c:f6:17:3d -net tap,id=n16 -vga virtio -display gtk -hda disk1.qcow2 -cdrom ubuntu-20.04.2-live-server-amd64.iso -boot c -smp 8 # Proceed with installation # Poweroff the machine # Power on with sudo -E kvm -m 4096 -netdev user,id=user.0 -device e1000,netdev=user.0 -device e1000,id=n1,mac=00:e0:4c:f6:02:3d -net tap,script=no,id=n1 -device e1000,id=n2,mac=00:e0:4c:f6:03:3d -net tap,id=n2 -device e1000,id=n3,mac=00:e0:4c:f6:04:3d -net tap,id=n3 -device e1000,id=n4,mac=00:e0:4c:f6:05:3d -net tap,id=n4 -device e1000,id=n5,mac=00:e0:4c:f6:06:3d -net tap,id=n5 -device e1000,id=n6,mac=00:e0:4c:f6:07:3d -net tap,id=n6 -device e1000,id=n7,mac=00:e0:4c:f6:08:3d -net tap,id=n7 -device e1000,id=n8,mac=00:e0:4c:f6:09:3d -net tap,id=n8 -device e1000,id=n9,mac=00:e0:4c:f6:10:3d -net tap,id=n9 -device e1000,id=n10,mac=00:e0:4c:f6:11:3d -net tap,id=n10 -device e1000,id=n11,mac=00:e0:4c:f6:12:3d -net tap,id=n11 -device e1000,id=n12,mac=00:e0:4c:f6:13:3d -net tap,id=n12 -device e1000,id=n13,mac=00:e0:4c:f6:14:3d -net tap,id=n13 -device e1000,id=n14,mac=00:e0:4c:f6:15:3d -net tap,id=n14 -device e1000,id=n15,mac=00:e0:4c:f6:16:3d -net tap,id=n15 -device e1000,id=n16,mac=00:e0:4c:f6:17:3d -net tap,id=n16 -vga virtio -display gtk -hda disk1.qcow2 -smp 8 # Login and… sudo apt-get update sudo apt-get install ansible magic-wormhole sshpass ansible-galaxy install mrlesmithjr.netplan #Copy the unzipped attached files debug-systemd.yml and hosts to vm #at host wormhole send debug-systemd.yml wormhole send hosts #receive files at vm wormhole receive ... wormhole receive ... # Configure the hosts file properly with ssh credentials (an example is attached) ansible-playbook -i hosts debug-systemd.yml reboot #login and... networkctl -a # you will see a lot of failing/degraded/pending interfaces ip -br a # You will see a log of interfaces without ip ** Attachment added: "debug-systemd.yml.zip" https://bugs.launchpad.net/ubuntu/focal/+source/systemd/+bug/1912331/+attachment/5483521/+files/debug-systemd.yml.zip -- 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
** 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 receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
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 any more pods without getting "Could not enumerate addresses: No buffer space available" errors, so I *assumed* there's more to that patch than just the ReceiveBuffer setting. -- 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
> 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 for systemd-networkd.socket, right? If that's the case, I don't really think this is something valid for backporting; the buffer increase is just delaying the ENOBUF, and if more interfaces are added it may still happen. I believe the buffer size adjustment is a configuration issue for anyone using such a large number of interfaces. However, if I've misunderstood the bug or patch, or if there are problems with my evaluation of it, please provide specific steps and/or config to reproduce the problem, so we can evaluate what's needed for backporting to focal. For now, marking as wontfix. ** Changed in: systemd (Ubuntu Focal) Status: New => Won't Fix -- 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
** 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 overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
** 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 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 overrun" Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
** 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 => 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 overrun" Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
