Introduction

How to file

Thank you for taking the time to report this bug and helping to make Ubuntu better. 

Could you please provide the following information:

 * content of /var/log/daemon.log related to mysql processes:

    /var/log/daemon.log

 * apparmor audit messages related to mysqld:

    /var/log/kern.log

 * mysqld apparmor profile:

    /etc/apparmor.d/usr.sbin.mysqld

 * list of mysqld apparmor profiles:

    ls -l /etc/apparmor.d/usr.sbin.mysqld*

 * mysql configuration stripped of private information (such as password):

    /etc/mysql/my.cnf

 * extra mysql configuration from the conf.d directory:

    /etc/mysql/conf.d/

 * directory listing of mysql datadir (by default /var/lib/mysql):

    ls -l /var/lib/mysql


=======================
Relevant error messages

Debugging procedure

How to Triage

Stock Reply

AppArmor profile not updated

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that you're using a non-standard location for your data directory (datadir option in my.cnf). However mysqld apparmor profile (in /etc/apparmor.d/usr.sbin.mysqld) hasn't been updated to allow access to the custom directory.

See https://wiki.ubuntu.com/DebuggingApparmor for more information on how to update mysqld apparmor profile.

How to Forward

Known bugs

• The debian-sys-maint user is not available and thus the status script reports a failure from mysqld.
• Mysql configuration uses non-standard location for its data files and thus mysqld apparmor profile needs to be updated.

Non-bugs

CategoryBugSquad CategoryDebugging