On slow boots snapd falls into a initialization loop

Bug #1782602 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,
while debugging other issues I had a guest slowed down, so the setup would be like:

1. KVM guest with Cosmic (4 CPUs 2G memory)
2. slow down this guest by ~1/8 with cgroups (see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732028/comments/13)
3. inside this KVM guest run a KVM guest with TCG (no -enable-kvm) with Cosmic as well

What happens is that on early boot things are fine but when snapd is supposed to initialize it fails and enters a init-loop trying over and over again preventing the system to reach a usable state to log in.

Looks like this:
[FAILED] Failed to start Snappy daemon.
See 'systemctl status snapd.service' for details.
[ OK ] Stopped Snappy daemon.
         Starting Snappy daemon...
[ OK ] Started OpenBSD Secure Shell server.
[FAILED] Failed to start Snappy daemon.
See 'systemctl status snapd.service' for details.
[ OK ] Stopped Snappy daemon.
         Starting Snappy daemon...
[FAILED] Failed to start Snappy daemon.
See 'systemctl status snapd.service' for details.
[...]

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

It is iterating on both:
  snapd.seeded.service
  snapd.service

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

To be clear, I see and have no prove that it would prevent login eventually.
But it keeps spinning - and in my special case due to that consumes almost all CPU power that I have.
In a normal case it might just spin and be annoying, but less blocking.

Revision history for this message
John Lenton (chipaca) wrote :

Could you attach the output of `journalctl -u snapd`?

Revision history for this message
John Lenton (chipaca) wrote :

I think this is probably a dupe of lp:1782616; marking it as such.

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

Other bug subscribers

Remote bug watches

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