Snorby still needs MyISAM engine in the MySQL database instead of InnoDB

Snorby won’t work with InnoDB as database engine!

Some day I had dropped the entire database schema, for some reason. To get a new one, let Snorby install the new database and all the required tables, by typing:

But afterwards I could not log in anymore. What the hell…
The access log gave me an error number 500, internal server error. And in the error log there was this:

At the first moment I thought that it could be an issue with ruby or rails or rake or thor something like that. No it’s not!

I’ve tried several things, but nothing has changed. But then I took a brief look into the database, and I noticed, that now all tables had been set up with InnoDB engine.
It seems, that since MySQL 5.6 or 5.7, InnoDB is now the default engine setting.

When I switched back to MyISAM, everything was perfect again.

This has been proofed for Snorby 2.6.3. running on debian 8.6 with ruby 3.2.22, rake 11.3.0…


Leave a Reply

Your email address will not be published. Required fields are marked *