*** This bug is a duplicate of bug 917542 ***
https://bugs.launchpad.net/bugs/917542
I had the same issue. I could start MySQL again by placing the following in the
mysql configfile:
[mysqld]
innodb_force_recovery = 4
After that MySQL started successfully. I have no idea if this is
recommend, maybe the bug will appear again later. But for those
encountering this issue maybe this helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970366
Title:
apparmor denies unlink of mysql socket
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/970366/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
