Let's tone it down a bit Gary. He's both right and wrong. He wants
people to discuss the same root issue and this thread is mixed up with
several "me too" comments that may or may not be the same issue.
In my case it was simple as editing mysql.cnf and start getting AppArmor
DENIED errors.
--
Yo
Where should we post it then? AppArmor bug tracker? It's pretty annoying
to change 1 setting on mysql.cnf and then be denied restarting the MySQL
server because of that. Are my distro settings too tight? is it
apparmor? is it mysql?
--
You received this bug notification because you are a member o
How are they incorrect? It's pretty simple. Change a my.cnf setting once
or twice and restart. Then AppArmor comes in and messes everything up.
If you said that this should be reported to AppArmor then say that
instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Happened to me on a fresh DO droplet.
Ubuntu 16.04.2 LTS
mysql Ver 14.14 Distrib 5.7.17 (x86_64)
After two or three days of normal functioning. We had to start
optimizing MyISAM. So the first thing we changed
log_slow_queries = /var/log/mysql/mysql-slow.log
long_query_time = 3
log-queries-not-u
