[Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"

[David Cunningham]

Hi Dan, thanks for that. Interestingly it was much harder to reproduce
the problem with debugging enabled, but we got it on about the 15th try.
The log is attached.


** Attachment added: "systemd-networkd-1.log"
   https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+attachment/5498612/+files/systemd-networkd-1.log

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1928733

Title:
  Starting systemd Network Service fails with "Invalid argument"

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This server has a new install of Ubuntu 18.04 server. Sometimes
  (around 50% of the time) when it boots systemd-networkd.service
  initially fails to start with an error as below. It then tries again
  and succeeds, however other services which depend on systemd-networkd
  have already failed on the dependency by then.

  From the output of "journalctl -u systemd-networkd":

  -- Reboot --
  May 17 19:44:28 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to set up mount namespacing: Invalid argument
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=226/NAMESPACE
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
  May 17 19:44:30 server1 systemd[1]: Failed to start Network Service.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.
  May 17 19:44:30 server1 systemd[1]: Stopped Network Service.
  May 17 19:44:30 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed
  May 17 19:44:30 server1 systemd[1]: Started Network Service.
  May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us
  May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP
  May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP
  May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier
  May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.46
  ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Mon May 17 19:53:11 2021
  InstallationDate: Installed on 2021-03-18 (60 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R440
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 transparent_hugepage=never
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.3
  dmi.board.name: 04JN2K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R440
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+subscriptions