Thanks for the bug report. As of version 1:11.8.6-4 mariadb now has an apparmor profile in enforce mode, and by default accepts having a data directory in /var/lib/mysql or /var/lib/mariadb. If you want to use a custom data directory you can allow it by adding an entry to the local apparmor profile file in /etc/apparmor.d/local/mariadbd.
In this case you can add the following lines to fix denials: /data/mysql/ r, /data/mysql/** rwk, then restart apparmor with systemctl restart apparmor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2146390 Title: mariadb fails to start with Apparmor 5.0.0-beta1-0ubuntu3 on Resolute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2146390/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
