Further info: My database is located on a separate disk, and I have amended the "datadir" entry in /etc/mysql/maridb.conf.d/50-server.cnf to point to the correct database location. This has worked fine up until about 2 days ago after updating my development system. So I tried making a bind mount of my database location on /var/lib/mysql and resetting 50-server.cnf back to standard and now the server is starting correctly. So I guess there is a new apparmor profile (or something) that doesn't allow for the fact that the database may have been moved...
I can work around it for the time being with the bind mount but I think this needs to be dealt with properly, as I suspect a lot of serious database users regularly relocate their databases. -- 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
