Disabling AppArmor may not be desirable solution, but as you see there could be error in apparmor's mysql configuration and then in configuration of mysql itself. When you disable apparmor for debugging you are one step ahead because mysql now actually produces some logs why it can't start (eg in my case some option that just needed to be commented. I doubt that mysqld would run with proper mysql conf and misconfigured apparmor).
-- CPU information is inaccessible for MySQL https://bugs.launchpad.net/bugs/448656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
