Stopping apparmor then restarting mysql then stopping mysql and starting
apparmor and starting mysql while apparmor is started works fine over
here.
Updated to 10.10.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ub
This solved my problem on Ubuntu Lucid:
apt-get remove --purge mysql-server mysql-common mysql-client
apt-get install mysql-server
After purging and installing the packages, mysql started fine. Seems it
was mysql-related.
--
You received this bug notification because you are a member of Ubuntu
I am also not able to start the mysql process successfully, even after
adding the line "/sys/devices/system/cpu/ r," to
/etc/apparmor.d/usr.sbin.mysqld. Did an update of packages apt-get
install mysql-client mysql-client-5.1 mysql-client-core-5.1 on ubuntu
lucid. After this, when starting mysql wit
I'm using ubuntu 9.10 and was having those messages on /var/log/syslog when
trying to stop mysql.
Added the line "/sys/devices/system/cpu/ r," to the end of "directories
listing" (before the last "}") of /etc/apparmor.d/usr.sbin.mysqld and now the
messages stopped... but i can't stop mysql yet.
This bug was fixed in the package mysql-dfsg-5.1 - 5.1.41-3ubuntu6
---
mysql-dfsg-5.1 (5.1.41-3ubuntu6) lucid; urgency=low
* debian/apparmor-profile: Upate apparmor profile. Get rid of annoying warning
when starting mysql. (LP: #79)
-- Chuck ShortThu, 18 Feb 2010 13:54:
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
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
Raising importance, between this bug and Bug #448656 and no telling how
many others, this is affecting a number of users.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Importance: Low => Medium
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notification
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
Made changes to apparmor, still mysql will not start.
Also did not have skip-bdb in my.cnf.
After restarting apparmor, I did notice that a few error messages disappeared,
and after deleting ibdata1 and ib_logfile0 and ib_logfile1 at least I am
getting completely different errors now, so there may
I don't even have skip-bdb in /etc/mysql/my.cnf, so commenting it out
isn't the solution. Using mysql 5.3.37 probided by mysql-server-5.1 on
Ubuntu 9.10 / Karmic.
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notification because you are a member o
Note to above post: The solution was found in this post: http://www
.mail-archive.com/debian-bugs...@lists.debian.org/msg189569.html
--
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
What worked for me was to mark out skip-bdb in the my.cnf file
I have attached the my.cnf file
** Attachment added: "the mysql configuration file"
http://launchpadlibrarian.net/34672629/my.cnf
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notif
This is my kern.log:
[10360.109659] type=1503 audit(1256893798.480:502): operation="open" pid=23026
parent=23025 profile="/usr/sbin/mysqld" requested_mask="r::" denied_mask="r::"
fsuid=0 ouid=0 name="/sys/devices/system/cpu/"
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/
This is my daemon.log
mysqld_safe: Starting mysqld daemon with databases from /home/mysqldata
Oct 30 10:09:44 trond-laptop mysqld: 091030 10:09:44 [Note] Plugin 'FEDERATED'
is disabled.
Oct 30 10:09:44 trond-laptop mysqld: /usr/sbin/mysqld: Table 'mysql.plugin'
doesn't exist
Oct 30 10:09:44 tron
Also tried to add the deny /sys/devices/system/cpu/ r, rule
Started apparmor OK
Starting mysql - Not OK
--
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-dfsg-5.1
** Tags added: apparmor
--
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-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.
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
I get long delays in my boot process just around this error:
Oct 7 09:37:11 maxwell kernel: [ 13.893332] input: HDA Digital PCBeep as
/devices/pci:00/:00:1b.0/input/input8
Oct 7 09:37:11 maxwell kernel: [ 15.370647] __ratelimit: 9 callbacks
suppressed
Oct 7 09:37:11 maxwell kernel
Can you add the following to your /etc/apparmor.d/usr.sbin.mysqld:
deny /sys/devices/system/cpu/ r,
Regards
chuck
--
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 mys
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
Does this failure affect mysqld behavior, except from logging this line
to syslog ?
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided => Low
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: New => Triaged
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
22 matches
Mail list logo
