Ok Robie Basak, You can now consider the original post an official bug report. I am getting the same log entries as Richard except the fsuid for my server log is 107. This is the second time on version 16.04.1 and first time on 16.04.2 that this has happened. The only permanent fix I have found os to do a clean install of the server software and hope it goes longer than last install before it blows up.
I believe the conflict is the way apparmor deals with mysql in the start up phase at boot. One curious behavior that I have found is that there seems to be a connection with the introduction of webmin server to the queue at startup. In the future, please do not discount a bug report simply because only one user has reported the issue. If one user has experienced the issue, then it is a near certainty that at least 10% of the user base has run into the same exact issue. They just don't have the time or experience to detail the circumstances that brought up the issue in the first place. Not all users are programmers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610765 Title: mysql server fails to start due to faulty apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1610765/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
