I have experienced this for the last few months, each time mysql is upgraded. A
workaround that works for me is:
1. stop apparmor [/etc/init.d/apparmor stop ]
2. stop mysql (probably not necessary) [ /etc/init.d/mysql stop ]
3. start mysql [ /etc/init.d/mysql start ]
4. start apparmor [/etc/init
I have experienced mysql failing to start for the last 2 months, after
an Ubuntu upgrade, and this failure to start could be worked around by
stopping apparmor. I have now added the line proposed in the original
posting, and mysql now appears to start satisfactorily when apparmor is
running. My exp
