Mysql – Unable to enable InnoDB in theSQL on Ubuntu 10.04

innodbMySQL

I am trying to enable InnDB on my linux server. I have installed Ubuntu 10.04 JeOS on an ESX server. I then installed mySQL and tomcat using aptitude. However when I use SHOW ENGINES; in mySQL it does not appear that InnoDB was installed. I then tried following the directions in the documentation. http://dev.mysql.com/doc/refman/5.1/en/innodb.html However I get the following when trying to enable a plugin:

ERROR 1123 (HY000): Can't initialize function 'InnoDB'; Plugin initialization function failed.

I would appreciate some advice as to how to approach this problem.

Best Answer

I had the same issue. In 10.04, apparmor does not allow MySQL to read the InnoDB plugins. Add the following lines to /etc/apparmor.d/usr.sbin.mysqld:

/usr/lib/mysql/plugin/ r, /usr/lib/mysql/plugin/* mr,

Then reload apparmor and restart the MySQL service.

Related Solutions

Mysql – thesqld crashes on any statement

See here: http://bugs.mysql.com/bug.php?id=44030

Philip S

I had the same issue. I tried upgrading from 5.1.33 to 5.1.36, but mysqld would still crash whenever accessing the database.

Some details, most of it probably irrelevant, but maybe something will pop out: This is a brand new laptop, and I just started on a new project. MD Turion X2 Dual-Core Mobile RM-74 w/4GB RAM DB size on disk is 1.67GB 1GB of RAM is being used as a ramdisk Fresh install of 5.1.33 on MS Vista 64 using the WAMP project installer. A lot of ALTERs, as this is a dev environment. Adding columns, indexes, etc. Renaming columns as well. The bug cropped up between coding sessions rather than during a coding session. All db schema was created using MySQL Administrator, and all data manipulation done using php and mysqli. Everything wrt MySQL is brand new. I'm sorry, I'm unable to provide data files.

Anyway, as the upgrade didn't work to allow me to access the data, and a lot of work occurred since my last backup, I wanted to restore/retrieve as much of the DB schema as possible, I wasn't concerned with data. I actually did retrieve most of the data as well. While I'm sure the process can be optimized, what worked for me is: C:\wamp\bin\mysql\mysql5.1.36\bin>mysqlshow.exe -u root then for each table C:\wamp\bin\mysql\mysql5.1.36\bin>mysqlshow.exe -u root until I got the error mysqlshow.exe: Cannot list columns in db: , table: : Lost connection to MySQL server during query then I restarted mysqld, started the MySQL console, and \u drop table for the table which caused the crash. After that, everything was back to normal other than the loss of the one small table which I should be able to recreate easily.

Mysql – Restoring a slave MySQL database from raw backups of master gives InnoDB tablespace errors

I believe that you have an incosistent snapshot especially due to the error

InnoDB: Error: tablespace id is 150238 in the data dictionary  
InnoDB: but in file ./1_107789/email.ibd it is 150747!

It may not LVM's fault. Googling here and here, it's my guess that you need to make sure mysql has written everything to the disks (no buffers) and that changes won't happen by lock'ing tables to be on the safe side. It could also be due to the different MySQL versions on the small chance that something has changed in the innodb code. You could rule this out by trying that exact snapshot on a clone/(similar server) of your master. Please see this too

Best Answer

Related Solutions

Mysql – thesqld crashes on any statement

Mysql – Restoring a slave MySQL database from raw backups of master gives InnoDB tablespace errors

Related Topic