** This bug is no longer a duplicate of bug 79
missing apparmor access rule
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in Ubuntu.
https://bugs.launchpad.net/bugs/377268
Title:
package mysql-server-5.0 5.1.3
Can you double-check that
a) really this line makes mysql start again (just remove that line, restart
apparmor and try to restart mysql)
b) you really started mysql *after* apparmor
I just double-checked this issue on my system and mysql 5.1 will start
without problems with the proposed line miss
To everyone having problems with not starting mysql daemons:
This bug (or better: omission) does *not* prevent mysql from starting - it just
produces a message in the syslog about a denied file access.
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug
Using
deny /sys/devices/system/cpu/ r,
seems to just suppress the message but makes no difference to
functionality (access to /sys/devices/system/cpu/ is denied and
/proc/stat accessed instead).
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notif
No, not that I have noticed. Mysqld seems to access /proc/stat if
/sys/devices/system/cpu/ is not accessible.
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfs
Public bug reported:
Testing with mysql-server-5.1 5.1.37-1ubuntu4 on Karmic Beta1, I get the
following error message in /var/log/syslog after starting mysqld:
kernel: [86913.526900] type=1503 audit(1254826475.203:56): operation="open"
pid=19633 parent=19632 profile="/usr/sbin/mysqld" requested_