Why is InnoDB disabled? (SOLVED)

HoKe - Sat, 2009/01/10 - 23:34

Support

after installing Drupal 6 appliance i do have problem to enable InnoDB in MySQL.

can some one help me please?

Thx

Innodb in enabled by default

Liraz Siri - Sun, 2009/01/11 - 12:13.

InnoDB is enabled by default, you don't have to do anything.

If you log in to PhpMyAdmin and go to the "Storage Engines" section, you'll notice that InnoDB is not disabled.

See the MySQL manual for more information (13.2.3. InnoDB Configuration).

my.cnf

HoKe - Sun, 2009/01/11 - 23:53.

in my.cnf is skip-innodb commented out = enabled innodb in mysqld. I tried to run live system to see defaults and realised following:


mysql> show engine innodb status;

ERROR 1235 (42000): Cannot call SHOW INNODB STATUS because skip-innodb is defined

mysql>

please help ;) if possible
thx in advance

I can't reproduce this...

Liraz Siri - Mon, 2009/01/12 - 09:19.

I booted the version of the appliance you are using in live mode (I.e., without installation) and the InnoDB engine is enabled, as it should be.

If you want me to try and investigate/reproduce your problem you are going to have to give me a great deal more information:

* what version of the appliance are you using?
* are you using the appliance in live mode or installed to a hard drive?
* what kind of machine or virtual machine is running the appliance? how much memory does it have?
* did you reconfigure mysql in any way?
* could you try starting over and see what it takes to reproduce this problem?

demanded answers

HoKe - Mon, 2009/01/12 - 23:27.

no problem to give you requested information
turnkey-drupal6-2008.10.28-hardy-x86
Live mode. 8GB HDD ready but not used for installation
VM - VirtualBox-2.1.0-41146-Win_x86.msi
512 MB RAM
no reconfiguration
I did only following:
mysql -u root -p
inserted password
mysql> show engine innodb status;
ERROR 1235 (42000): Cannot call SHOW INNODB STATUS because
skip-innodb is defined
mysql> show engines;
InnoDB |DISABLED

news

HoKe - Mon, 2009/01/19 - 22:22.

finaly I found a solution.

/etc/init.d/mysql stop
mv /var/lib/mysql/ib_logfile0 /var/lib/mysql/ib_logfile0.bak
mv /var/lib/mysql/ib_logfile1 /var/lib/mysql/ib_logfile1.bak

/etc/init.d/mysql start

now it works! great ;)

Your innodb log files were corrupt?

Liraz Siri - Tue, 2009/01/20 - 04:40.

I did a little research on why your solution works and it seems that though InnoDB is enabled by default, MySQL seems to disable it automatically if your InnoDB log files get corrupted. When you remove them, they are recreated, allowing InnoDB to start again.

Thanks for sharing!

Thanks!

Ryan B (not verified) - Sun, 2009/12/20 - 05:10.

Thanks for the tip! This solved the problem for me also.

setting InnoDB as default mysql storage engine

Alon Swartz - Mon, 2009/01/12 - 12:59.

As Liraz mentioned, InnoDB is enabled by default.

# mysql -uroot
> show engines;
 MyISAM     | DEFAULT
 InnoDB     | YES
 ...

But if you want it to be your default storage engine you have to specify it, for example:

# cat /etc/mysql/conf.d/storage_engine.cnf
[mysqld]
default-storage-engine = InnoDB

# /etc/init.d/mysql restart

# mysql -uroot
> show engines;
 MyISAM     | ENABLED
 InnoDB     | DEFAULT
 ...

Why is InnoDB disabled? (SOLVED)

Innodb in enabled by default

my.cnf

I can't reproduce this...

demanded answers

news

Your innodb log files were corrupt?

Thanks!

setting InnoDB as default mysql storage engine

Thank you

This helped me, too!

Thanks

Post new comment

Appliance categories

You are here:

Post new comment

Appliance categories