MySQL Bugs: #9971: Can't enable Innodb

Bug #9971	Can't enable Innodb
Submitted:	18 Apr 2005 13:49	Modified:	18 Apr 2005 14:40
Reporter:	Daniel Parry	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	mysql-standard-4.1.11	OS:	Linux (linux)
Assigned to:		CPU Architecture:	Any

Description:
On a multi-processor redhat 9 box, I have found it impossible to enable innodb on the mysql-standard-4.1.11-pc-linux-gnu-i686 binary version of mysql. I wonder if it is anything to do with the kernel version being used:

Linux version 2.4.20-8bigmem (bhcompile@porky.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Thu Mar 13 17:32:29 EST 2003

How to repeat:
e.g. just create any table with the engine set to innodb:

CREATE TABLE `foo` ( ... ) ENGINE=innodb;

and the table type will drop back to MyISAM?

We're sorry, but the bug system is not the appropriate forum for 
asking help on using MySQL products. Your problem is not the result 
of a bug.

Support on using our products is available both free in our forums
at http://forums.mysql.com and for a reasonable fee direct from our
skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Additional info:

Make sure skip_innodb is not in effect.

With identical configuration files, init scripts, and mysql tarballs innodb is working perfectly fine for me on a red hat fedora core 3 system. I am not asking for help on the installation - I am reporting that an install that works fine on one box does not work on another. Bug? Could be?

Daniel,
Does the error log of the server mention anything about InnoDB being started? MySQL will default to MyISAM if InnoDB is not available (not included in the mysqld executable, or disabled by skip_innodb).

Eeek. Sorry. Turned out I was getting bitten by running multiple mysql instances on the same machine... feel free to close this. Apologies for taking up your time and thanks for helping.