I found that the bond seems not to have come up properly: $ sudo cat /proc/net/bonding/bond-lan Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2+3 (2) MII Status: down MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: fast Min links: 0 Aggregator selection policy (ad_select): stable System priority: 65535 System MAC address: 5e:07:b7:b3:1d:bd bond bond-lan has no active aggregator Slave Interface: p3p4 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 3c:fd:fe:77:32:cb Slave queue ID: 0 Aggregator ID: N/A Slave Interface: p3p3 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 3c:fd:fe:77:32:ca Slave queue ID: 0 Aggregator ID: N/A -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: New Bug description: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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
