>From what I can see in the logs this does not appear to be the issues Tyler and Stephane have mentioned, however I can't entirely rule that issue out yet.
The logs in comment 1 do not match up with the error reported in the bug description, but appear to be the same as from comment 8, however the error messages and profile load messages do match up, so we do have some correlation. Interestingly I see no logging of a change_profile failure on apparmor's part, which should generally be happening with this kernel. Could we enable apparmor debug and disable ratelimiting on these machines? echo 1 >/sys/module/apparmor/parameters/debug echo 0 >/proc/sys/kernel/printk_ratelimit and see if that will provide us any more info for this error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667444 Title: Failed to start lxd container because it is already running a start operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1667444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
