[Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
ok sounds like this needs to be addressed in netplan. ** Package changed: systemd (Ubuntu) => nplan (Ubuntu) ** Changed in: nplan (Ubuntu) Importance: Undecided => High ** Changed in: nplan (Ubuntu) Status: Incomplete => Triaged ** Changed in: nplan (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Also affects: nplan (Ubuntu Artful) Importance: High Assignee: Mathieu Trudel-Lapierre (cyphermox) Status: Triaged -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in nplan package in Ubuntu: Triaged Status in nplan source package in Artful: Triaged Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
Finally found a work-around that also proves the failure to become configured is caused by that stupid ipv6ll address added to the DNS server list. But I did not find any way which integrates into netplan. I basically took /run/systemd/network/10-netplan-br0.network and copied it as /etc/systemd/network/05-br0.network. Then added: "IPv6AcceptRA=no" to the [Network] section and rebooted. Now the DNS list only contains the one server I specify and the status ends up as "routable (configured)". -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
So that link local is from a Wireless AP that runs open-wrt. But why it is picked up and how can I stop this madness? -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
Started to bring up real HW with the same woes and timeout on boot. After some more cursing and faffing around I realized an odd element of the resulting setup: There is some weird ipv6 link local address for DNS server: fe80::c66e:1fff:fe3b:bdcd. It is the same for the VM doing dhcp and for real HW where I manually set everything and that does *not* include any fancy ipv6 address. Matter of fact I cannot enter any ipv6 address in the nameservers address section without getting complaints about unexpected ':'s. But that is another story. So does anybody have a clue were that comes from? It is not in the generated netplan files in /run/systemd/network but systemd-resolvd gets it (probably from /run/systemd/netif/links/*). -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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
Re: [Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
On Wed, Jun 14, 2017 at 05:58:06PM -, Ryan Harper wrote: > This is a known issue w.r.t waiting for IPV6 LL, on Xenial KVM, qemu -net > user does not provide IPV6 LL response (yakkety and newer do), so there's a > delay; it does sound like the IPV6 LL timeout is longer than it used to be > as I've seen a 5 to 10 second delay in VMs launched on KVM on xenial, but > not a full 120 seconds which breaks the wait-online. If it were just a delay, networkd should still eventually recognize the device as configured. Maybe some packets are going missing? We probably need a network trace from within the guest. Also probably interesting to know if 'sudo service networkd-resolved restart' changes the state of things, or if the device remains 'configuring'. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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
Re: [Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
This is a known issue w.r.t waiting for IPV6 LL, on Xenial KVM, qemu -net user does not provide IPV6 LL response (yakkety and newer do), so there's a delay; it does sound like the IPV6 LL timeout is longer than it used to be as I've seen a 5 to 10 second delay in VMs launched on KVM on xenial, but not a full 120 seconds which breaks the wait-online. On Wed, Jun 14, 2017 at 12:31 PM, Stefan Baderwrote: > So from what Steve wrote and what I see. the missing part is moving from > "Gained IPv6LL" to "Configured". > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1697730 > > Title: > Long boot time due to systemd-networkd-wait-online.service failure > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ > 1697730/+subscriptions > -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
So from what Steve wrote and what I see. the missing part is moving from "Gained IPv6LL" to "Configured". -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
@Ryan: 2: eth0 Link File: /lib/systemd/network/99-default.link Network File: /run/systemd/network/10-netplan-eth0.network Type: ether State: routable (configuring) Path: xen-vif-0 Driver: vif HW Address: 00:16:3e:71:31:57 (Xensource, Inc.) Address: 192.168.2.159 fe80::216:3eff:fe71:3157 Gateway: 192.168.2.1 (PC Engines GmbH) DNS: 192.168.2.1 fe80::c66e:1fff:fe3b:bdcd Similar on the KVM guest, just being ens3 then. -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
I noticed one difference between our configs was that you did not have public ipv6 set up. I shut down radvd on my router and rebooted as a test; this seems to cause a slight delay at boot (long enough for systemd to send a message warning that it's waiting for the network to be configured), but this takes about 15s before it gives up on ipv6, not 2 minutes. -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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
Re: [Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
What does your networkctl status eth0 show? On Wed, Jun 14, 2017 at 11:34 AM, Ryan Harperwrote: > It looks a lot like this issue: > > https://github.com/systemd/systemd/issues/1645 > > Where DHCP works, it has an ip and can sync time and other items, but the > wait service isn't happy. > > On Wed, Jun 14, 2017 at 10:46 AM, Steve Langasek < > steve.langa...@canonical.com> wrote: > >> The journal shows, two minutes after the start of the wait-online job: >> >> Jun 14 00:11:42 bar-artful6401 systemd-networkd-wait-online[618]: Event >> loop failed: Connection timed out >> Jun 14 00:11:42 bar-artful6401 systemd[1]: >> systemd-networkd-wait-online.service: >> Main process exited, code=exited, status=1/FAILURE >> Jun 14 00:11:42 bar-artful6401 systemd[1]: Failed to start Wait for >> Network to be Configured. >> Jun 14 00:11:42 bar-artful6401 systemd[1]: >> systemd-networkd-wait-online.service: >> Unit entered failed state. >> Jun 14 00:11:42 bar-artful6401 systemd[1]: >> systemd-networkd-wait-online.service: >> Failed with result 'exit-code'. >> Jun 14 00:11:43 bar-artful6401 systemd[1]: Reached target Network is >> Online. >> >> So this sounds like a protocol/socket issue, rather than an issue with >> networkd reporting wrong state of the network devices. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1697730 >> >> Title: >> Long boot time due to systemd-networkd-wait-online.service failure >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/16977 >> 30/+subscriptions >> > > -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
It looks a lot like this issue: https://github.com/systemd/systemd/issues/1645 Where DHCP works, it has an ip and can sync time and other items, but the wait service isn't happy. On Wed, Jun 14, 2017 at 10:46 AM, Steve Langasek < steve.langa...@canonical.com> wrote: > The journal shows, two minutes after the start of the wait-online job: > > Jun 14 00:11:42 bar-artful6401 systemd-networkd-wait-online[618]: Event > loop failed: Connection timed out > Jun 14 00:11:42 bar-artful6401 systemd[1]: > systemd-networkd-wait-online.service: > Main process exited, code=exited, status=1/FAILURE > Jun 14 00:11:42 bar-artful6401 systemd[1]: Failed to start Wait for > Network to be Configured. > Jun 14 00:11:42 bar-artful6401 systemd[1]: > systemd-networkd-wait-online.service: > Unit entered failed state. > Jun 14 00:11:42 bar-artful6401 systemd[1]: > systemd-networkd-wait-online.service: > Failed with result 'exit-code'. > Jun 14 00:11:43 bar-artful6401 systemd[1]: Reached target Network is > Online. > > So this sounds like a protocol/socket issue, rather than an issue with > networkd reporting wrong state of the network devices. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1697730 > > Title: > Long boot time due to systemd-networkd-wait-online.service failure > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ > 1697730/+subscriptions > ** Bug watch added: github.com/systemd/systemd/issues #1645 https://github.com/systemd/systemd/issues/1645 -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
Fresh install of an artful-server image in a VM, and I can't reproduce this problem. For some reason, on your system networkd never logs that the network interface has been 'configured'. So in fact, systemd- networkd-wait-online is behaving correctly; you're somehow just never getting the OK from systemd-networkd. ubuntu@artful-server:~$ time sudo /lib/systemd/systemd-networkd-wait-online ignoring: lo real0m0.018s user0m0.012s sys 0m0.000s ubuntu@artful-server:~$ echo $? 0 ubuntu@artful-server:~$ ip link 1: lo:mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:68:21:e2 brd ff:ff:ff:ff:ff:ff ubuntu@artful-server:~$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:68:21:e2 brd ff:ff:ff:ff:ff:ff inet 192.168.15.68/24 brd 192.168.15.255 scope global dynamic ens3 valid_lft 3269sec preferred_lft 3269sec inet6 2001:470:e980:0:5054:ff:fe68:21e2/64 scope global mngtmpaddr noprefixroute dynamic valid_lft 86295sec preferred_lft 14295sec inet6 fe80::5054:ff:fe68:21e2/64 scope link valid_lft forever preferred_lft forever ubuntu@artful-server:~$ cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: ens3: dhcp4: yes dhcp6: yes ubuntu@artful-server:~$ cat /run/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] DHCP=yes [DHCP] RouteMetric=100 ubuntu@artful-server:~$ dpkg -l systemd|grep ^ii ii systemd233-6ubuntu3 amd64system and service manager ubuntu@artful-server:~$ And, perhaps most crucially: ubuntu@artful-server:~$ sudo journalctl -u systemd-networkd --no-pager -- Logs begin at Wed 2017-06-14 09:20:15 PDT, end at Wed 2017-06-14 09:27:38 PDT. -- Jun 14 09:20:17 artful-server systemd[1]: Starting Network Service... Jun 14 09:20:17 artful-server systemd-networkd[451]: Enumeration completed Jun 14 09:20:17 artful-server systemd[1]: Started Network Service. Jun 14 09:20:17 artful-server systemd-networkd[451]: ens3: IPv6 successfully enabled Jun 14 09:20:17 artful-server systemd-networkd[451]: ens3: Gained carrier Jun 14 09:20:18 artful-server systemd-networkd[451]: ens3: DHCPv4 address 192.168.15.68/24 via 192.168.15.1 Jun 14 09:20:18 artful-server systemd-networkd[451]: ens3: Gained IPv6LL Jun 14 09:20:20 artful-server systemd-networkd[451]: ens3: Configured ubuntu@artful-server:~$ -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]:
[Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
Hm, maybe that helps. This is the contents of /run/systemd/netif/links/2 (which is my eth0): # This is private data. Do not parse. ADMIN_STATE=configuring OPER_STATE=routable NETWORK_FILE=/run/systemd/network/10-netplan-eth0.network DNS=192.168.2.1 fe80::c66e:1fff:fe3b:bdcd NTP= DOMAINS= ROUTE_DOMAINS= LLMNR=yes MDNS=no ADDRESSES=192.168.2.159/24 ROUTES=192.168.2.1/32/0/100/254/18446744073709551615 0.0.0.0/0/0/100/254/18446744073709551615 DHCP4_ADDRESS=192.168.2.159 DHCP_LEASE=/run/systemd/netif/leases/2 ADMIN_STATE sounds suspicious. -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
@Steve, eth0 is normal when you use Xen HVM guests. What I see when I strace the wait command is that is is in some epoll most of the time. That was the reason I was thinking that maybe it is waiting on some status change. But then I also believe it did find two entries in /run/systemd/netif/links which seem to be lo and eth0. So it should be aware of both. Just not sure what it is waiting for. -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
The journal shows, two minutes after the start of the wait-online job: Jun 14 00:11:42 bar-artful6401 systemd-networkd-wait-online[618]: Event loop failed: Connection timed out Jun 14 00:11:42 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jun 14 00:11:42 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 14 00:11:42 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 14 00:11:42 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Jun 14 00:11:43 bar-artful6401 systemd[1]: Reached target Network is Online. So this sounds like a protocol/socket issue, rather than an issue with networkd reporting wrong state of the network devices. -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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
Re: [Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
On Wed, Jun 14, 2017 at 10:04:28AM -, Stefan Bader wrote: > Sorry, forgot above: > #> cat /run/systemd/network/10-netplan-eth0.network > [Match] > Name=eth0 > [Network] > DHCP=ipv4 > [DHCP] > RouteMetric=100 I know you say this is also reproducible for you when using ensX names, but for completeness, why do you have eth0 here? That's not a name that should be appearing anywhere on an artful system, unless you've set net.ifnames=0, which is strongly discouraged. On Wed, Jun 14, 2017 at 07:37:50AM -, Stefan Bader wrote: > @Steve, yes it does. And if the wait is related to the list of NICs from > ifquery, it does make sense (in some way) as that list only contains > "lo", not "eth0". Also "ifquery --state eth0" does not return anything > while it does return "lo=lo" for "lo". networkd doesn't care at all about ifquery. systemd-networkd-wait-online(8) documents that this should return as soon as "all links it is aware of and which are managed by systemd-network [are] fully configured or failed, and [...] at least one link [gains] a carrier." So this is definitely not working as designed, if you have only a single interface configured in systemd-network and its link is up, but -wait-online is not returning success. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
This is annoying: % journalctl -D var/log/journal -o short-precise Journal file var/log/journal/1fe5c5ed88c14c81bd52acb9f96f3a18/system.journal uses an unsupported feature, ignoring file. -- No entries -- Why can't xenial systemd journalctl read an artful one? That seems like a terrible idea w.r.t features here; are we enabling new features that we can't read outside of the same distro release? https://bugzilla.redhat.com/show_bug.cgi?id=1413388 We should get this fixed when it;s available. Or disable the LZ4 for compat until it's done On Wed, Jun 14, 2017 at 5:04 AM, Stefan Baderwrote: > Sorry, forgot above: > > #> cat /run/systemd/network/10-netplan-eth0.network > [Match] > Name=eth0 > > [Network] > DHCP=ipv4 > > [DHCP] > RouteMetric=100 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1697730 > > Title: > Long boot time due to systemd-networkd-wait-online.service failure > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ > 1697730/+subscriptions > ** Bug watch added: Red Hat Bugzilla #1413388 https://bugzilla.redhat.com/show_bug.cgi?id=1413388 -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
Sorry, forgot above: #> cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] DHCP=ipv4 [DHCP] RouteMetric=100 -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
Here the netcat config. Note only eth0 appearing here (for KVM guests, the same happens but with ensX NIC names). ** Attachment added: "01-netcfg.yaml" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+attachment/4895673/+files/01-netcfg.yaml -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
I created the directory and rebooted once ;) Here is the tarball. ** Attachment added: "journal.tgz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+attachment/4895674/+files/journal.tgz -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
@Steve, yes it does. And if the wait is related to the list of NICs from ifquery, it does make sense (in some way) as that list only contains "lo", not "eth0". Also "ifquery --state eth0" does not return anything while it does return "lo=lo" for "lo". -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
Is this delay reproducible post-boot if you run '/lib/systemd/systemd- networkd-wait-online' from the commandline? ** Changed in: systemd (Ubuntu) Status: New => 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: Incomplete Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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
Re: [Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
And what about /etc/netplan/*.yaml and /run/systemd/network/* If you can attach the journal binary file, we can query the state independently from you tar up /run/log/journal/ Thanks On Tue, Jun 13, 2017 at 11:33 AM, Stefan Baderwrote: > #> ifquery --list > lo > > #> ip link show > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode > DEFAULT group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: eth0: mtu 1500 qdisc mq state UP > mode DEFAULT group default qlen 1000 > link/ether 00:16:3e:71:31:57 brd ff:ff:ff:ff:ff:ff > > #> ifconfig > eth0: flags=4163 mtu 1500 > inet 192.168.2.159 netmask 255.255.255.0 broadcast 192.168.2.255 > inet6 fe80::216:3eff:fe71:3157 prefixlen 64 scopeid 0x20 > ether 00:16:3e:71:31:57 txqueuelen 1000 (Ethernet) > RX packets 1879 bytes 290874 (290.8 KB) > RX errors 0 dropped 255 overruns 0 frame 0 > TX packets 1052 bytes 390313 (390.3 KB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10 > loop txqueuelen 1000 (Local Loopback) > RX packets 326 bytes 24232 (24.2 KB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 326 bytes 24232 (24.2 KB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1697730 > > Title: > Long boot time due to systemd-networkd-wait-online.service failure > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ > 1697730/+subscriptions > -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: New Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias:
[Touch-packages] [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
#> ifquery --list lo #> ip link show 1: lo:mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:71:31:57 brd ff:ff:ff:ff:ff:ff #> ifconfig eth0: flags=4163 mtu 1500 inet 192.168.2.159 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 fe80::216:3eff:fe71:3157 prefixlen 64 scopeid 0x20 ether 00:16:3e:71:31:57 txqueuelen 1000 (Ethernet) RX packets 1879 bytes 290874 (290.8 KB) RX errors 0 dropped 255 overruns 0 frame 0 TX packets 1052 bytes 390313 (390.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 326 bytes 24232 (24.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 326 bytes 24232 (24.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: New Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure
** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.10 -- 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/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure Status in systemd package in Ubuntu: New Bug description: Fresh VM installation from the Artful daily server ISO. Installation finishes without issues but booting the installed system takes a long time (until systemd-networkd-wait-online.service times out). The VM can already be pinged at that stage, so network has been configured at that stage. It just seems that the waiting command does not notice the interface being up. From the installed system (after timeout) it looks like the lo device is set up via /etc/network/interfaces but the NIC is set in /etc/netplan/01-netcfg.yaml. systemd-networkd.service: Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service... Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service. Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1 Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL systemd-networkd-wait-online.service (failed): Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured... Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state. Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 13 18:11:47 2017 InstallationDate: Installed on 2017-06-13 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.8.0 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.8.0 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+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