Default storage engine (InnoDB) is not available

Nachdem mich diese Fehlermeldung heute um den (eh schon angekratzten) Verstand gebracht hat – nein, natürlich gibt es im MySQL-Server von Debian weiterhin InnoDB, aber Kopieren von alten Konf-Dateien erfordert Umsicht…

Die Lösung gefunden habe ich dann dort* und möchte mich Khaled anschließen, das Problem paßt _definitiv_ nicht zur Fehlermeldung und der Grund ist mir auch schleierhaft…

*) und da sage noch mal einer was gegen Blogs

Update 2011-03-10
Mir ist gerade aufgefallen, dass khaled-labidi.net gerade tot ist (ja, ich hatte das Problem wieder…)

Ich habe mal den Text aus dem Google-Cache gekratzt, Urheberrechtsverletzung hin oder her:

Default storage engine (InnoDB) is not available
September 13, 2008, 9:06 pm

That’s the big issue I was facing this morning when starting the MySQL service version 5.0.67/Win32. The first step I took is to simply look for a google-looked-up page that deals with this issue, and it was the mysql forums. However, I found the diffrent exposed solutions a lot radical as almost of them tend to a backup-delete-reinstall strategy, and it does not really suit my needs. So the first thing I’ve done is to try starting the mysql service in the console debug mode :
D:\mysql\bin>mysqld-debug.exe –console

and the output was very explicit about the possible roots of the innoDB issue :
InnoDB: Error: log file .\ib_logfile0 is of different size 0 25165824 bytes
InnoDB: than specified in the .cnf file 0 10485760 bytes!
080913 13:24:24 [ERROR] Default storage engine (InnoDB) is not available
080913 13:24:24 [ERROR] Aborting
080913 13:24:24 [Note] mysqld-nt.exe: Shutdown complete

So basically, the MySQL service is complaining about a mismatch between the effective innoDB log file size on the disk (24MB), and the defined size (10MB) within the my.ini file. So changing the my.ini property would help solving the issue :
innodb_log_file_size=24M

A little attenion should be paid to another property in my.ini file which is innodb_buffer_pool_size as its value is impacted by the innodb_log_file_size setting. After this simple setting, the service was correctly started. No data/log backup, deletion required, nor service reinstallation. Nevertheless, I still not understand the real issue behind this file size mismatch…