[Bug 1722300] Re: Boot times since artful upgrade have increased 4 fold

[Chris Gregan]

Fixed by multiple apt-get update calls. Seems the networking bug in systemd
was preventing me from getting the updated version that fixed the
networking issue.

On Mon, Oct 9, 2017 at 2:31 PM, Dimitri John Ledkov <launchpad at surgut.co.uk>
wrote:

> Please reboot?
>
> /me goes to fix all ubuntu mirrors in the world
>
> does it work now? cool.
>
> http://www.commitstrip.com/en/2015/02/17/have-you-tried-turning-it-off-
> and-on-again/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1722300
>
> Title:
>   Boot times since artful upgrade have increased 4 fold
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
> 1722300/+subscriptions
>


-- 
Chris Gregan
Quality Assurance Manager
Field Engineering/CPE
cgregan at irc.canonical.com

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

Title:
  Boot times since artful upgrade have increased 4 fold

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd:
    Installed: 234-2ubuntu10

  
  I'm seeing a much longer bot time in Artful than I did in Zesty. Systemd-analyze blame indicates that systemd is at the root of this issue.

  hris at Thermia:~$ sudo systemd-analyze blame
        2min 541ms lxd-containers.service
        2min 213ms systemd-networkd-wait-online.service
            6.260s NetworkManager-wait-online.service
            4.342s plymouth-quit-wait.service
            1.108s fwupd.service
             838ms lxd.service
             690ms snapd.service
             567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
             374ms dev-loop8.device
             353ms dev-loop9.device
             340ms dev-loop10.device
             312ms dev-loop4.device

  Syslog shows:
  chris at Thermia:~$ cat /var/log/syslog | grep systemd-networkd-wait-online.service
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
  chris at Thermia:~$ ubuntu-bug

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