Ubuntu
network-manager package

NetworkManager-wait-online.service slows down boot

Bug #1723809 reported by NickS
76
This bug affects 17 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After upgrade to artful, boot is considerable slower. By using systemd-analyze blame I've managed to narrow it to NetworkManager-wait-online.service.
         30.591s NetworkManager-wait-online.service
         10.240s nmbd.service
          9.273s postfix@-.service
          9.110s apt-daily.service
          6.485s dev-sdb1.device
          5.488s ModemManager.service
          5.318s udisks2.service
          4.968s accounts-daemon.service
          3.807s fwupd.service
          3.049s grub-common.service
          2.837s apport.service
          2.764s NetworkManager.service
          2.413s speech-dispatcher.service
          2.362s snapd.service
          2.160s networking.service
          2.083s pppd-dns.service
          2.078s lm-sensors.service
          2.073s gpu-manager.service
          2.066s alsa-restore.service
          1.570s smbd.service
          1.380s rsyslog.service
          1.310s polkit.service
          1.117s apparmor.service

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Mon Oct 16 00:18:09 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.1 dev enp2s0 proto static metric 100
 169.254.0.0/16 dev enp2s0 scope link metric 1000
 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.3 metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:

SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Wired connection 1 066da907-ea49-35a2-8b54-b829cc834081 /org/freedesktop/NetworkManager/ActiveConnection/2
 enp0s18f2u2 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- --
 enp0s18f2u2i2 ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.8.4 connected started full enabled enabled enabled enabled enabled

Revision history for this message
NickS (nstojic66) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Nawaf Al-Subaie (nalsubaie) wrote :

This bug cropped up a few days ago.

 2min 107ms systemd-networkd-wait-online.service
          3.916s plymouth-quit-wait.service
          3.013s iio-sensor-proxy.service
          1.557s snapd.service
          1.119s systemd-backlight@backlight:intel_backlight.service
           991ms apparmor.service
           900ms fwupd.service
Changing the timeout limit from 5 min to 5 sec did not make any difference

Revision history for this message
Dimitrios Piliouras (jimpil1985) wrote :

This affects me as well :(. Here is the output of `systemd-analyze time`:

Startup finished in 2.283s (kernel) + 36.155s (userspace) = 38.438s

And here is the output of `systemd-analyze blame`:

         30.025s NetworkManager-wait-online.service
          4.142s vboxdrv.service
          3.692s plymouth-quit-wait.service
          2.646s postgresql@9.5-main.service
          1.454s snapd.service
          1.446s dev-sda1.device
          1.348s grub-common.service
          1.163s fwupd.service
          1.136s apport.service
          1.134s speech-dispatcher.service
           884ms apparmor.service
           828ms pulseaudio.service
           752ms colord.service
           349ms ufw.service

So basically from the 36 seconds it took to boot, 30 of them were for NetworkManager-wait-online.service.

Revision history for this message
Karsten Tausche (kt42) wrote :

I am using Ubuntu 17.10 on different machines and noticed this problem only on a machine that was upgraded from earlier Ubuntu version. It does not affect my clean 17.10 installations. Could this be affected by (incompatible) settings of previous releases?

By the way, NetworkManager-wait-online.service blocks for around 30s even if the machine is connected to a wired network.

Revision history for this message
Max (mxmax) wrote :

Karsten Tausche, I have a clean install and the service is blocking for 8 secs.

That's still pretty slow, considering my system didn't take too long too boot up in other releases of Ubuntu (~15 secs before, it's now 25 secs).

Revision history for this message
Brad Love (b-rad) wrote :

Real hardware running Bionic, MSI b350m prog motherboard with R3 1300x cpu. I must use a usb ethernet due to the onboard ethernet causing PCIe issues. I thought the extended freeze I was experiencing at boot up was caused by hardware driver issues I'm debugging, since I do not even get a log blurb if I hard reset, but I just happened to notice it is this bug by disabling quiet and splash.

The wait-online-service check *never* finishes for me when it is triggered. I've left the PC on in this state for over an hour and it never reached the desktop. I don't know what triggers it, but lately it seems I experience it nine times out of ten boots.

If I boot without the usb ethernet connected (PCIe ethernet drivers disabled) the boot starts immediately.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.