David, the trouble is most of the comments here are for various
different local configuration changes. You'd be best served by filing a
new bug. If you have DENIED lines from AppArmor, make sure your logs
include them.
Thanks
--
You received this bug notification because you are a member of
After all that, my mysqld is still broken. I see no "valid" ticket for
this bug linked here, if this one is invalid. Where is the bug report
for the root cause?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
--
Basak. You were wrong at the beginning and your still wrong. The bug is
mysql and apparmor dont work together. Period. I havent had any problems at
all no matter what configuration i had as soon as I uninstalled mysql and
loaded another database. Please quit telling people there is nothing wrong
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
My position is still the same. It seems that everyone piling on to this
bug report with a "me too" is not affected by the same root cause as the
original reporter, who had a problem with a locally customised AppArmor
profile that ended up incorrect and which we identified was not a bug.
The
I don't know if it's the case here, but I've seen *new* apparmor
profiles not being applied because the apparmor cache file had, for some
reason, a more recent timestamp. That made the system use the cache file
instead of the correct changed config file.
--
You received this bug notification
I don't know if it's the case here, but I've seen *new* apparmor
profiles not being applied because the apparmor cache file had, for some
reason, a more recent timestamp. That made the system use the cache file
instead of the correct changed config file.
--
You received this bug notification
So, I have become very good at checking the MySQL setup, and in my case
(I recently restarted my server) I had AppArmor properly setup but it
still would not work
My previous actions, as pointed out, disabled AppArmor why it after that
started working
@seth-arnold Seth Arnold pointed out the
The DENIED of /proc//status is tracked in bug #1658239
The DENIED of /sys/devices/system/node/ is tracked in bug bug #1658233
@cripperz I think the above cover the changes you had to made to your
profile. Let's track these issues over there and keep this bug for
apparmor errors regarding the
The DENIED of /proc//status is tracked in bug #1658239
The DENIED of /sys/devices/system/node/ is tracked in bug bug #1658233
@cripperz I think the above cover the changes you had to made to your
profile. Let's track these issues over there and keep this bug for
apparmor errors regarding the
@andreas
Just a description how this happened again. Usually it would happen after the
server lost power and reboot this error would come back. Or the VM abruptly off
without a proper shutdown then i will hit into this issue.
root@ns3:/etc/mysql#apparmor_parser -r -T -W -v
Where is the output of "sudo apparmor_parser -r -T -W -v
/etc/apparmor.d/usr.sbin.mysqld"?
--
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:
Apparmor refuses mysqld open on
Where is the output of "sudo apparmor_parser -r -T -W -v
/etc/apparmor.d/usr.sbin.mysqld"?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.7 in Ubuntu.
Matching subscriptions: main
https://bugs.launchpad.net/bugs/1610765
Aug 18 20:07:53 ns3 audit[7045]: AVC apparmor="DENIED" operation="open"
profile="/usr/sbin/mysqld" name="/proc/7045/status" pid=7045 comm="mysqld"
requested_mask="r" denied_mask="r" fsuid=111 ouid=111
I just stumbled again into the problem. took the chance to try your suggest
@andreas
below
@cripperz, can you please try regenerating the apparmor cache and
reloading it, via this command:
sudo apparmor_parser -r -T -W -v /etc/apparmor.d/usr.sbin.mysqld
Then restart mysql:
sudo service mysql restart
--
You received this bug notification because you are a member of Ubuntu
Server
@cripperz, can you please try regenerating the apparmor cache and
reloading it, via this command:
sudo apparmor_parser -r -T -W -v /etc/apparmor.d/usr.sbin.mysqld
Then restart mysql:
sudo service mysql restart
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just bumped into this error with my Ubuntu 16.04 LTS Server with
mysql-5.7
-- Unit mysql.service has begun starting up.
Aug 09 19:49:46 ns3 audit[3405]: AVC apparmor="DENIED" operation="open"
profile="/usr/sbin/mysqld" name="/proc/3405/status" pid=340
Aug 09 19:49:46 ns3 audit[3405]: AVC
** 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:
Apparmor refuses mysqld open on /etc/mysql/my.cnf.migrated causing
MySQL started to throw apparmor errors after enabling slow-query-logs.
I haven't used this log option for quite some time. So it probably sat for a
few years (and several migrations) uncommented in my my.cnf.
It turned out that the variable name had changes. The entry used to be
Sorry Robie but you are still wrong. It is a bug but mostly because mysql
is more the problem and not Ubuntu. Changing databases does fix the bug.
Changing ubuntu doesn't make the bug go away.
Gary
On Apr 21, 2017 6:39 AM, "Robie Basak" <1610...@bugs.launchpad.net>
wrote:
> I think it's time to
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
I think it's time to mark this bug Invalid. We have had a bunch of "me
too" comments that are clearly and incorrectly describing bugs other
than the one described here.
Conversely the only credible explanation of the problem reported
(failure to start due to AppArmor denial of
Actually I got similar problem, when tuning setting I added
table_cache= 256
into /etc/mysql/mysql.conf.d/mysqld.cnf file
--
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:
I just realized some strange behaviour with my
mysqld Ver 5.7.17-0ubuntu0.16.04.1 for Linux on x86_64 ((Ubuntu))
this my.cmf parameter "default-character-set=utf8" in
/etc/mysql/mysql.conf.d/mysqld.cnf
caused this dmesg output:
audit: type=1400 audit(1491639131.263:200): apparmor="DENIED"
Zach, this bug appears to be growing to encompass too many things. I
suggest filing a new bug report if you think you've got an issue, and if
you think it's AppArmor related, please be sure to include any DENIED
lines from dmesg or audit logs.
Thanks
--
You received this bug notification
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
(This might be best put in a separate report, but adding it here for now)
The behavior was added for 5.7 with this change
https://github.com/mysql/mysql-server/commit/1bba7015030a1cdd9eba21d48e7fdd1bad16ebef
It is there to prevent one server process from setting the same socket
file as another,
I see this now on a plain, fresh install of MySQL 5.7:
[Fri Mar 31 12:50:59 2017] audit: type=1400 audit(1490957460.075:78):
apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
name="/proc/4988/status" pid=4988 comm="mysqld" requested_mask="r"
denied_mask="r" fsuid=112 ouid=112
As
@RN
> I just ran into Robie's problem at my site.
No, you didn't. You didn't get the message with
name="/etc/mysql/my.cnf.migrated" so you are not affected by this bug.
You are hitting a different bug - perhaps bug 1658239.
--
You received this bug notification because you are a member of
On Tue, Mar 28, 2017 at 04:26:52PM -, Paul Payne wrote:
> Actually, I'm getting a further apparmor error:
> AVC apparmor="STATUS" operation="profile_replace" profile="unconfined"
> name="/usr/sbin/mysqld"
This is not an error message. This is a status message that reports a new
AppArmor
Hello all. I have been trying to figure out just what is going on like
all of you. The problem is that Oracle has messed with mysql to the
point that it no longer works like it should. The fix is Mariadb, or any
other database program. I'm not into conspiracies but Oracle has a
vested interest
I don't know what the deal is. I can now start the mysqld with `sudo
systemctl start mysql`. However, when I interact with apt, e.g. `sudo
apt-get autoremove`, it attempts to complete the mysql configuration
step:
Setting up mysql-server-5.7 (5.7.17-0ubuntu0.16.04.2) ...
mysql_upgrade: Got error:
Actually, I'm getting a further apparmor error:
AVC apparmor="STATUS" operation="profile_replace" profile="unconfined"
name="/usr/sbin/mysqld"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610765
Same problem here. mike-something's solution fixed the issue for me. I
believe rnickle-hccoll's description is correct.
--
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:
Apparmor refuses
I ran into this problem when I upgraded my VM from 14.04 to 16.04.
mysql server no longer started, and after a re-install with
sudo apt purge mysql-server mysql-server-5.7 mysql-server-core-5.7
sudo apt install mysql-server
showed the errors stated
I shut them up with:
sudo nano
I just ran into Robie's problem at my site. I have a 16.04 server setup
in a VM running mysql 5.7.17 Community Edition.
About two weeks ago, we started having the mysqld throw apparmor errors
and die every day at a random time.
What appears to be happening is the daily apt update is trying to
I am not sure this will help anyone but i got this problem to go away
via: (I cannot cut and paste my logs so you may have to fill in the
middle sections)
I got the apparmor utilities and put mysql into complain only mode.
::aa-complain mysql
While this did help mysql run it didnt get much
Importance -> Low since we appear to have had only three reports in six
months, and it's coming up to a year since 16.04 was released. Therefore
I think it's reasonable to assume that this only affects unusual end-
user configurations, since typically when a bug affecting more MySQL
users appears
39 matches
Mail list logo
