= Managed to break Apparmor on my Ubuntu 20.04 VPS? =

![ ](httpswww.redditstatic.com/desktop2x/img/renderTimingPixel.png)

I have a Linode that I use to run a Wireguard VPN, MQTT broker, and a few other small things but somehow while getting everything setup as I wanted it I have apparently broken Apparmor somehow. I've been trying to troubleshoot this for a while and googling everything relevant that I can come up with but I'm not really getting anywhere.

I suspect maybe the kernel boot parameters are part of the issue but I haven't changed any of the defaults there and so I don't know why it would not be running. Any suggestions? Is fixing this even worth the hassle? Thanks in advance.

aa-status returns:

apparmor module is not loaded.

systemctl status apparmor says the following -

● apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Tue 2022-05-03 21:11:59 UTC; 6min ago └─ ConditionSecurity=apparmor was not met Docs: man:apparmor(7) httpsgitlab.com/apparmor/apparmor/wikis/home/ May 03 21:11:59 Ubuntu systemd[1]: Condition check resulted in Load AppArmor profiles being skipped.

**EDIT Problem solved by following this! I'm going to leave this post up in case it helps anyone in the future.

Following a reboot, a read of /proc/cmdline revealed that the kernel parameters were not used. This is because Linode defaults to using their own kernel, you will need to explicitly set GRUB 2 to boot in the Linode Manager.

Login to the Linode Manager, click the node relevant node and locate the 'Configuration Profile'. Change the kernel to 'GRUB 2'.

Reboot and see what happens. Good luck!


no comments yet

Be the first to share what you think!

== About Community ==