AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap-confine.snapd.21465 in /var/lib/snapd/apparmor/snap-confine.internal/cap-bpf at line 2

[watri]

I failed start snapd.apparmor after snapd update to 2.63+20.04ubuntu0.1.
The error the error log
Aug 02 08:35:16 ip-172-31-3-24 systemd[1]: Starting Load AppArmor profiles managed internally by snapd...
Aug 02 08:35:16 ip-172-31-3-24 snapd-apparmor[784359]: main.go:124: Loading profiles [/var/lib/snapd/apparmor/profiles/snap-confine.snapd.21465 /var/lib/snapd/apparmor/profiles/snap-confine.snapd.21759 /var/li>
Aug 02 08:35:16 ip-172-31-3-24 snapd-apparmor[784359]: error: cannot load apparmor profiles: exit status 1
Aug 02 08:35:16 ip-172-31-3-24 snapd-apparmor[784359]: apparmor_parser output:
Aug 02 08:35:16 ip-172-31-3-24 snapd-apparmor[784359]: AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap-confine.snapd.21465 in /var/lib/snapd/apparmor/snap-confine.internal/cap-bpf at line 2: In>
Aug 02 08:35:16 ip-172-31-3-24 systemd[1]: snapd.apparmor.service: Main process exited, code=exited, status=1/FAILURE
Aug 02 08:35:16 ip-172-31-3-24 systemd[1]: snapd.apparmor.service: Failed with result 'exit-code'.
Aug 02 08:35:16 ip-172-31-3-24 systemd[1]: Failed to start Load AppArmor profiles managed internally by snapd.

[Launchpad Janitor (janitor)]

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

[Alex Murray (alexmurray)]

Thanks for reporting this issue - can you please run 'apport-collect 2075580' from a terminal which should capture a bunch of details necessary to help identify what is happening here?

[Liam Best (liambest)]

Hi Alex, I've opened 2076575 and ran `apport-collect` on a machine that is having the same issues as the original reporter - I've marked my bug as a duplicate of this one.

[Alex Murray (alexmurray)]

Thanks Liam - unfortunately that didn't collect as much useful information as I was hoping. I suspect that what is happening here is a race condition between snapd and snapd.apparmor - could you also please run the snap-debug-info.sh script?

This will likely produce a lot of output so it would be worth redirecting it to a file and then attaching that here - so I suggest you run it as:

/snap/snapd/current/usr/lib/snapd/snap-debug-info.sh > ~/snap-debug-info.log 2>&1

Which will create a file in your home directory called snap-debug-info.log which you can then attach to this bug report. Thanks.

[Liam Best (liambest)]

Attached :)