*** This bug is a duplicate of bug 1421303 ***
https://bugs.launchpad.net/bugs/1421303
Ultimately, apparmor is the culprit. I noticed that the file
/etc/apparmor.d/usr.sbin.mysqld has a line:
/run/mysqld/mysqld.sock r,
Which means that the socket file will never be able to be written the
first time, which seems a bug to me. I made it this instead:
/run/mysqld/mysqld.sock rw,
Works great now. I made a bunch of changes and many files have been
edited. I think there may have been some other lines I edited, like:
/run/mysqld/mysqld.pid rw,
/var/log/mysql.log rw,
/var/log/mysql.err rw,
/etc/mysql/mysql.conf.d/** rw,
/etc/mysql/mysql.cnf rw,
/etc/mysql/my.cnf rw,
If you can't figure out, then temporarily disable apparmor and change
the apparmor profile until you get it working.
/etc/init.d/apparmor stop
Then mysql should work again:
/etc/init.d/mysql restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435080
Title:
mysql-server upgrade hangs dpkg --reconfigure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1435080/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
