Bug 6900

Summary:	Mariadb fails to start if InnoDB disabled but still the default
Product:	Mageia	Reporter:	dave pickles <mg>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	alien, mageia
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mariadb-5.5.25-1.mga2.src.rpm	CVE:
Status comment:

Description dave pickles 2012-07-29 15:29:45 CEST

Description of problem:
Following update of MariaDB from 5.5.23-4.mga2 to 5.5.25-1.mga2, the server failed to start. The log file contained:

120729 13:47:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/
mysql
120729 13:47:57 [Note] Plugin 'PBXT' is disabled.
120729 13:47:57 [Note] Plugin 'InnoDB' is disabled.
120729 13:47:57 [ERROR] Unknown/unsupported storage engine: InnoDB
120729 13:47:57 [ERROR] Aborting

repeated many times as the service tried to restart.

The config file /etc/my.cnf contained the following relevant lines:

#default-storage-engine = InnoDB
skip-innodb

It seems that in the new 5.5.25 version of MariaDB InnoDB is the default storage engine and the server cannot start if InnoDB is disabled - this was not a problem in 5.5.23. The solution was to change the two lines to read:

default-storage-engine = MyISAM
skip-innodb

ie to explicitly set a default engine which is not InnoDB.

Version-Release number of selected component (if applicable):


How reproducible:
Not tested on any other system but reproducible on this machine.

Steps to Reproduce:
1. Configure MariaDB as documented above
2. Update MariaDB to 5.5.25
3.

Manuel Hiebel 2012-07-29 16:03:25 CEST

Assignee: bugsquad => alien

Comment 1 Sander Lepik 2012-07-29 16:04:34 CEST

I don't see the problem here. Default my.cnf doesn't disable InnoDB. If you disabled it manually then you also have to change default engine.

Even MySQL on Mageia 1 doesn't disable InnoDB, so you had to do it manually.

Status: NEW => RESOLVED
CC: (none) => sander.lepik
Resolution: (none) => WORKSFORME
Assignee: alien => bugsquad

Comment 2 dave pickles 2012-07-29 16:29:09 CEST

I agree that my my.cnf file is illogical, at least since InnoDB became the default engine (mysql 5.5.5?). However it has worked for at least five years, first on mysql/Mandriva and right up to the last Mageia version 5.5.23.

I have now documented the change here, so hopefully anyone else with a similar setup will be able to find the solution ;-)

Comment 3 AL13N 2012-07-30 11:54:19 CEST

actually, it might be possible that 5.5.23 had forgotten to use innodb as default. but it is/was definately the idea that 5.5 branch, since GA, should have had innodb as default.

CC: (none) => alien