Comment 12 for bug 201799

Just had the same issue and followed the steps provided by Lost In Tokyo. This did not work for me. I then followed the steps by Kees Cook. Working fine with it disabled.

I spent at least 3 hours trying to figure out what the cause of the issue was. My logs are identical, except I am moving the data to another drive mounted on the system. This is on Jaunty.

In addition to apparmor disallowing mysql user to write to other directories, it also is preventing the memlock option from working which forces mysql to use additional system memory instead of the disk for buffers, etc, greatly increasing performance.

mysql-server: 5.1.30really5.0.75-0ubuntu10.2
apparmor: 2.3+1289-0ubuntu14