This is from a cosmic GCE instance _after_ the lxd snap has been seeded:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @23.527s
└─multi-user.target @23.527s
└─chrony.service @24.515s +57ms
└─basic.target @7.698s
└─sockets.target @7.687s
└─snap.lxd.daemon.unix.socket @21.088s
└─snap-lxd-9010.mount @15.903s +28ms
└─local-fs-pre.target @886ms
└─systemd-tmpfiles-setup-dev.service @851ms +21ms
└─systemd-sysusers.service @773ms +64ms
└─systemd-remount-fs.service @523ms +159ms
└─systemd-journald.socket @442ms
└─system.slice @428ms
└─-.slice @428ms
$ journalctl --boot 0 | pastebinit
http://paste.ubuntu.com/p/RYd5mDB76q/
$ ps fauxww | pastebinit
http://paste.ubuntu.com/p/yxKtVTTm9D/
(Before data coming up in a minute.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796137
Title:
huge and slow image 20181002 due to seeded lxd snap
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1796137/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
