*** This bug is a duplicate of bug 79 ***
https://bugs.launchpad.net/bugs/79
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported and
appears to be a duplicate, so it is being marked as such. Please
That is upgrade related issue as well, usually they both come hand in
hand (adding apparmor permission and commenting skip-bdb). I was
referring to this in my earlier post.
Glad you got it working now.
--
CPU information is inaccessible for MySQL
https://bugs.launchpad.net/bugs/448656
You receiv
following the thread at:
http://ubuntuforums.org/archive/index.php/t-1305921.html
I also solved the issue by commenting the following line:
skip-bdb
in /etc/mysql/my.cnf
long life toUbuntu!
:)
--
CPU information is inaccessible for MySQL
https://bugs.launchpad.net/bugs/448656
You received thi
The following worked for me
1. Edit /etc/apparmor.d/usr.sbin.mysqld and add the line
/sys/devices/system/cpu/ r,
2. Restart apparmor (as root): /etc/init.d/apparmor restart
--
CPU information is inaccessible for MySQL
https://bugs.launchpad.net/bugs/448656
You received this bug notification beca
Disabling AppArmor may not be desirable solution, but as you see there
could be error in apparmor's mysql configuration and then in
configuration of mysql itself. When you disable apparmor for debugging
you are one step ahead because mysql now actually produces some logs why
it can't start (eg in m
So, disabling AppArmor is not a proper solution, while MySQL may be
misconfigured.
--
CPU information is inaccessible for MySQL
https://bugs.launchpad.net/bugs/448656
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu
Suggestion: Add line
/sys/devices/system/* r,
to your /etc/apparmor.d/usr.sbin.mysqld
Then check your syslog/mysql-log again if there is something else e.g. i
personnaly had problem with package in kubuntu. After adding rule I saw
error in log complaining about bdb something. I opened /etc/mysql
This is caused by AppArmor, if you stop AppArmor via
/etc/init.d/apparmor stop
start Mysql via
/etc/init.d/mysql start
My Sql will run and you can now restart apparmor via
/etc/init.d/apparmor start
Now I try to find the necessary setting for the apparmor profile.
Cheers,
Ihon
--
CPU info
Confirmed on fresh Kubuntu 9.10:
after calling /etc/init.d/mysql script server fails to start an dmesg shows
following:
17672.383215] type=1503 audit(1257090344.464:108): operation="open"
pid=23872 parent=23871 profile="/usr/sbin/mysqld" requested_mask="r::"
denied_mask="r::" fsuid=0 ouid=0 name=
2JBB: No, using only default values from package. Data folders have
right permissions, and as I suppose it really shouldn't depend on it.
vitaly:/var/lib$ ls -l mysql
total 28764
-rw-r--r-- 1 mysql mysql0 2009-10-08 12:18 debian-5.1.flag
-rw-rw 1 mysql mysql 18874368 2009-11-01 03:17
You may have a permission issue. Did you change the directories mysql
is accessing. For me, this was resolved by granting the mysql user
under which mysql runs access to the relevant directories (/log/mysql
/lib/mysql /etc/mysql).
i.e.,
chown -R mysql:mysql
--
CPU information is inaccessible
I got the same errors in syslog, added
/sys/devices/system/cpu/ r,
and
/sys/devices/system/* r,
to the apparmor config for mysql, but no go.
upgraded 9.04 to 9.10, i have my database in a non standard folder,
mentioned in the apparmor file since 9.04.
--
CPU information is inaccessible for MySQ
This also happens when you try and reinstall mysql-server
[ 634.638825] type=1503 audit(1256857087.602:77): operation="open" pid=4201
parent=4200 profile="/usr/sbin/mysqld" requested_mask="r::" denied_mask="r::"
fsuid=0 ouid=0 name="/sys/devices/system/cpu/"
Error message in window:
E: mysql-s
Same goes here.
[ 634.638825] type=1503 audit(1256857087.602:77): operation="open"
pid=4201 parent=4200 profile="/usr/sbin/mysqld" requested_mask="r::"
denied_mask="r::" fsuid=0 ouid=0 name="/sys/devices/system/cpu/"
--
CPU information is inaccessible for MySQL
https://bugs.launchpad.net/bugs/4
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Incomplete => Confirmed
--
CPU information is inaccessible for MySQL
https://bugs.launchpad.net/bugs/448656
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
For me, yes it does.
--
CPU information is inaccessible for MySQL
https://bugs.launchpad.net/bugs/448656
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@list
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Does this prevent mysql from starting correclty?
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided => Low
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: New => Incomplete
--
CPU information
17 matches
Mail list logo
