Plesk and apparmor (feature request)

[LaurentR2D2]

Hello,

I've noticed each time I install Plesk on Ubuntu that bind9 doesn't start because of apparmor. Until today, I was removing apparmor from the system. I've found another way to do by modifying its config file like indicated below :

http://www.failover.co/blog/plesk-11-bind9-and-ubuntu-12-04-apparmor-problems

Is it possible to have an apparmor package shipped with this modification in a future release of Plesk ? I would be easier, even if the modification is easy to perform. I don't reinstall Plesk every day, and between two reinstalls I generally forget this apparmor problem is here, and I have to search to understand why suddenly my DNS doesn't work

 

[IgorG]

Actually AppArmor is not supported by Parallels Plesk Panel (Plesk). Sometimes AppArmor can interfere with Plesk installation or functionality.

 

[LaurentR2D2]

Actually AppArmor is not supported by Parallels Plesk Panel (Plesk). Sometimes AppArmor can interfere with Plesk installation or functionality.

So the best is to remove it completely instead of doing what is suggested in the article ?

 

[IgorG]

Yes, just remove it.

 

[LaurentR2D2]

Yes, just remove it.

I wanted to follow this tuto :

http://www.techytalk.info/disable-and-remove-apparmor-on-ubuntu-based-linux-distributions/

sudo /etc/init.d/apparmor stop

sudo update-rc.d -f apparmor remove

sudo apt-get --purge remove apparmor apparmor-utils libapparmor-perl libapparmor1

but i leads to remove a lot of packages :

The following packages will be REMOVED:
accountsservice* apparmor* colord* dbus* dbus-x11* gconf2* gvfs*
gvfs-daemons* language-selector-common* libapparmor-perl* libapparmor1*
libgnome2-0* libgnome2-bin* libgnome2-common* libgnomevfs2-0*
libgnomevfs2-common* libpam-systemd* policykit-1* policykit-1-gnome*
systemd-services* ubuntu-standard* udisks2*

So I've decided to remove apparmor only, and not libapparmor-perl and libapparmor1. Is it enough ?

 

[UFHH01]

Hi LaurentR2D2,

this is absolutely enough - you don't even have to remove apparmor, after "update-rc.d -f apparmor remove", but to have a "clean" system, the removal can be recommended.

 

[trialotto]

@LaurentR2D2 (and @everyone),

As UFHH01 implicitly or explicitly stated, it is not necessary to remove apparmor completely.

Moreover, the lack of support by Plesk for apparmor does not imply that Plesk cannot run properly and without problems with appropriate apparmor configuration.

In short, you can optionally use the workaround, presented in the online article with the link provided.

Note (however) that Plesk will also work properly without specific apparmor profiles activated AND that a workaround is still a workaround (not a proper solution), hence implying that is good practice to disable the specific apparmor profiles and configuration settings.

In short, it is desirable to use the out-of-the-box Plesk installation and configuration, i.e. no specific apparmor workarounds.

Kind regards....