On Mon, Mar 06, 2017 at 09:11:06PM -, Gary Mercer wrote:
> ok. The "bug" is reproducible. It has happened on every time i have
> installed ubuntu 16.04 (all iterations). It is quirky because if you do
> a reboot three times in a row, the error message goes away and apparmor
> allows mysql to
ok. The "bug" is reproducible. It has happened on every time i have
installed ubuntu 16.04 (all iterations). It is quirky because if you do
a reboot three times in a row, the error message goes away and apparmor
allows mysql to start without any errors. on the same machine with
exactly the same
@Gary
Look, I want to help. Please see "How to Report Bugs Effectively" at
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for an excellent
explanation as to why I cannot help right now.
> You can now consider the original post an official bug report.
Unfortunately the bug status will
Ok. You guys have had way too long to at least post something besides
"this isn't a bug" retort to the original post. BTW, that was back in
August of last year. Most of us who have taken the time to look into
solutions to the issue would like to know that at least some programmer
somewhere in the
** Changed in: mysql-5.7 (Ubuntu)
Status: Invalid => Confirmed
--
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
Same thing is happening to me. Just started after some package upgrades.
I have never touched the AppArmor config nor the MySQL config. I wound
up disabling AppArmor in the meantime just so that I can get my database
server up again.
Mar 03 20:09:28 oddnetwork.org audit[4215]: AVC
This happens to me as well, 16.04 with the following log:
Mar 2 16:39:06 paulpc kernel: [ 1622.002136] audit: type=1400
audit(1488494346.712:224): apparmor="DENIED" operation="open"
profile="/usr/sbin/mysqld" name="/proc/19772/status" pid=19772 comm="mysqld"
requested_mask="r" denied_mask="r"
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
I have the same issue, but this time, with Ubuntu Xenial 16.04 running
on Vagrant, for both the ubuntu/xenial64 and the bento/ubuntu-16.04
images. Unfortunately, Richard's fix didn't work for me either, and I
had no choice but to revert back to 14.04.
--
You received this bug notification
Aha, so it will likely fail on next reboot again.
Another mysql-server troubleshooting session in my near future :)
--
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
On Mon, Aug 08, 2016 at 09:05:14PM -, Richard wrote:
> The following commands were required to successfully start:
> service mysql stop
> systemctl restart apparmor.service
> service mysql start
Please note that "systemctl restart apparmor.service" is dangerous;
systemd implements "restart"
That is true, if I remove my line again, it still works.
mysql-server-5.7:amd64 was updated on 160724
When my server was rebooted on 2016-08-07, mysql would not start with the
following syslog output:
c505 kernel: [ 1485.490459] audit: type=1400 audit(1470619337.926:98):
apparmor="DENIED"
According to
http://wiki.apparmor.net/index.php/QuickProfileLanguage#File_Globbing,
/etc/mysql/** will match any file or directory in or below /etc/mysql/.
So this should work. If it isn't working for you, I suspect that you
have an unrelated issue that inadvertently got fixed when you edited the
I did change it when there were other apparmor bugs.
The problem is that this line, that I have, does not work:
/etc/mysql/** r
Adding this line fixes the problem:
/etc/mysql/* r,
I don't know apparmor well, but it appears two stars do not work here.
--
You received this bug notification
Thank you for your report.
I believe this has happened because you have a locally modified
/etc/apparmor.d/usr.sbin.mysqld. The one we ship has "/etc/mysql/** r"
which includes /etc/my.cnf.migrated.
If you still think this is a bug in Ubuntu, please explain, provide
exact steps to reproduce and
15 matches
Mail list logo
