Not the reporter but having a similar issue. When the systemd package is updated my bond dies (with the "speed changed to 0 for port" message). Nothing that I have tried to restore the network connection worked short of a full reboot. I have attached my syslog showing what occurs during the upgrade.
I also see the following during this time: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond The LACP configuration on the switch is identical for all servers with bonds, but the only ones having this problem are the ones running bionic (trusty & xenial are unaffected). I will try to find some time to see if I can reproduce with a simple 'systemctl restart systemd-networkd' -- 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/1824806 Title: Network stops working after systemd update Status in systemd package in Ubuntu: Confirmed Bug description: I have four 18.04 servers that are regularly updated and have a bond/bridge configured via netplan. Every so often the interfaces themselves will have "speed changed to 0" and the server will be unresponsive over network. The servers are still usable via the console, though. I think I can confidently associate it with systemd updates. If I'm manually updating the servers, e.g., `apt dist- upgrade`, and there's a system update... the ssh session becomes unresponsive when updating systemd, timing of automatic security updates seems to coincide with it happening as well. Rebooting fixes the issue until the next systemd update. I've included some log excerpts and one of my netplan configs below. Thanks! syslog: `Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: Lost carrier Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host kernel: [1058497.661292] igb 0000:04:00.3 enp4s0f3: speed changed to 0 for port enp4s0f3 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: Lost carrier Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host systemd[1]: Started Network Time Synchronization. Apr 9 06:39:01 stn-vm-host systemd[1]: Stopped Flush Journal to Persistent Storage. Apr 9 06:39:01 stn-vm-host systemd[1]: Stopping Flush Journal to Persistent Storage... Apr 9 06:39:01 stn-vm-host kernel: [1058497.732487] systemd[1]: Stopping Journal Service... Apr 9 06:39:01 stn-vm-host kernel: [1058497.732903] systemd-journald[672]: Received SIGTERM from PID 1 (systemd). Apr 9 06:39:01 stn-vm-host kernel: [1058497.823634] igb 0000:04:00.2 enp4s0f2: speed changed to 0 for port enp4s0f2 Apr 9 06:39:01 stn-vm-host kernel: [1058497.833718] systemd[1]: Stopped Journal Service. Apr 9 06:39:01 stn-vm-host kernel: [1058497.837652] systemd[1]: Starting Journal Service... Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: Lost carrier Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host systemd[1]: Starting Flush Journal to Persistent Storage... Apr 9 06:39:01 stn-vm-host kernel: [1058497.912976] systemd[1]: Started Journal Service. Apr 9 06:39:01 stn-vm-host systemd[1]: Started Flush Journal to Persistent Storage. Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host kernel: [1058497.971223] igb 0000:04:00.1 enp4s0f1: speed changed to 0 for port enp4s0f1 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: Lost carrier Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host kernel: [1058498.109063] igb 0000:04:00.0 enp4s0f0: speed changed to 0 for port enp4s0f0 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Gained carrier Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Configured Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: br0: Configured` Apt history, noting the systemd update just before the interfaces when down `Start-Date: 2019-04-09 06:38:55 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19) End-Date: 2019-04-09 06:39:06` The netplan config on this server: `network: ethernets: enp4s0f0: addresses: [] dhcp4: false dhcp6: false enp4s0f1: addresses: [] dhcp4: false dhcp6: false enp4s0f2: addresses: [] dhcp4: false dhcp6: false enp4s0f3: addresses: [] dhcp4: false dhcp6: false bonds: bond0: dhcp4: false dhcp6: false interfaces: - enp4s0f0 - enp4s0f1 - enp4s0f2 - enp4s0f3 parameters: lacp-rate: slow mode: 802.3ad transmit-hash-policy: layer2 bridges: br0: interfaces: [bond0] dhcp4: no dhcp6: no addresses: [10.0.0.1/16] gateway4: 10.0.0.10 nameservers: addresses: [10.0.0.10,8.8.8.8] search: - lan version: 2` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
