[Bug 880339] Re: AppArmor profile needs update

[Andres Rodriguez]

Hi Jurgen,

Have you installed any databases in a different location than the
default one? Cause I've seen issues like yours but only when changing
the location of the databases. Other than that, I have re-tested this in
another clean install without any issues. Could you please attach the
apparmor profile file?

Install log:

roaksoax at pursue:~$ sudo apt-get install mysql-server
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libdbd-mysql-perl mysql-client-5.1 mysql-client-core-5.1 mysql-server-5.1 mysql-server-core-5.1
Suggested packages:
  tinyca
The following NEW packages will be installed:
  libdbd-mysql-perl mysql-client-5.1 mysql-client-core-5.1 mysql-server mysql-server-5.1 mysql-server-core-5.1
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/20.9 MB of archives.
After this operation, 53.6 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Preconfiguring packages ...
Selecting previously deselected package libdbd-mysql-perl.
(Reading database ... 232434 files and directories currently installed.)
Unpacking libdbd-mysql-perl (from .../libdbd-mysql-perl_4.019-1_amd64.deb) ...
Selecting previously deselected package mysql-client-core-5.1.
Unpacking mysql-client-core-5.1 (from .../mysql-client-core-5.1_5.1.58-1ubuntu1_amd64.deb) ...
Selecting previously deselected package mysql-client-5.1.
Unpacking mysql-client-5.1 (from .../mysql-client-5.1_5.1.58-1ubuntu1_amd64.deb) ...
Selecting previously deselected package mysql-server-core-5.1.
Unpacking mysql-server-core-5.1 (from .../mysql-server-core-5.1_5.1.58-1ubuntu1_amd64.deb) ...
Selecting previously deselected package mysql-server-5.1.
Unpacking mysql-server-5.1 (from .../mysql-server-5.1_5.1.58-1ubuntu1_amd64.deb) ...
Selecting previously deselected package mysql-server.
Unpacking mysql-server (from .../mysql-server_5.1.58-1ubuntu1_all.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up libdbd-mysql-perl (4.019-1) ...
Setting up mysql-client-core-5.1 (5.1.58-1ubuntu1) ...
Setting up mysql-client-5.1 (5.1.58-1ubuntu1) ...
Setting up mysql-server-core-5.1 (5.1.58-1ubuntu1) ...
Setting up mysql-server-5.1 (5.1.58-1ubuntu1) ...
mysql start/running, process 24002
Setting up mysql-server (5.1.58-1ubuntu1) ...

Syslog:


Nov 15 11:30:42 pursue mysqld[23794]: 
Nov 15 11:30:42 pursue mysqld[23794]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
Nov 15 11:30:42 pursue mysqld[23794]: To do so, start the server, then issue the following commands:
Nov 15 11:30:42 pursue mysqld[23794]: 
Nov 15 11:30:42 pursue mysqld[23794]: /usr/bin/mysqladmin -u root password 'new-password'
Nov 15 11:30:42 pursue mysqld[23794]: /usr/bin/mysqladmin -u root -h pursue password 'new-password'
Nov 15 11:30:42 pursue mysqld[23794]: 
Nov 15 11:30:42 pursue mysqld[23794]: Alternatively you can run:
Nov 15 11:30:42 pursue mysqld[23794]: /usr/bin/mysql_secure_installation
Nov 15 11:30:42 pursue mysqld[23794]: 
Nov 15 11:30:42 pursue mysqld[23794]: which will also give you the option of removing the test
Nov 15 11:30:42 pursue mysqld[23794]: databases and anonymous user created by default.  This is
Nov 15 11:30:42 pursue mysqld[23794]: strongly recommended for production servers.
Nov 15 11:30:42 pursue mysqld[23794]: 
Nov 15 11:30:42 pursue mysqld[23794]: See the manual for more instructions.
Nov 15 11:30:42 pursue mysqld[23794]: 
Nov 15 11:30:42 pursue mysqld[23794]: Please report any problems with the /usr/scripts/mysqlbug script!
Nov 15 11:30:42 pursue mysqld[23794]: 
Nov 15 11:31:09 pursue kernel: [ 5635.540221] type=1400 audit(1321374669.381:26): apparmor="STATUS" operation="profile_load" name="/usr/sbin/mysqld" pid=23974 comm="apparmor_parser"
Nov 15 11:31:09 pursue kernel: [ 5635.566068] type=1400 audit(1321374669.409:27): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=23998 comm="apparmor_parser"
Nov 15 11:31:10 pursue /etc/mysql/debian-start[24023]: Upgrading MySQL tables if necessary.
Nov 15 11:31:10 pursue /etc/mysql/debian-start[24027]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Nov 15 11:31:10 pursue /etc/mysql/debian-start[24027]: Looking for 'mysql' as: /usr/bin/mysql
Nov 15 11:31:10 pursue /etc/mysql/debian-start[24027]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Nov 15 11:31:10 pursue /etc/mysql/debian-start[24027]: This installation of MySQL is already upgraded to 5.1.58, use --force if you still need to run mysql_upgrade
Nov 15 11:31:10 pursue /etc/mysql/debian-start[24034]: Checking for insecure root accounts.
Nov 15 11:31:10 pursue /etc/mysql/debian-start[24038]: Triggering myisam-recover for all MyISAM tables

For this reason, I'm marking this bug as invalid as I'm unable to
reproduce it. If you still experience this issue and you believe this
bug should remain open, please feel free to re-open this bug.

Thank you!

** Changed in: mysql-5.1 (Ubuntu Oneiric)
       Status: Incomplete => Invalid

** Changed in: mysql-5.1 (Ubuntu Precise)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/880339

Title:
  AppArmor profile needs update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/880339/+subscriptions