mySQL error 1033

If you ever come across this error after having to do an emergency reformat of a server (ugh) it’s usually because the innodb settings changed in the my.cnf file.

The easy way to fix this is to delete your ib_logfile* files in /var/lib/mysql and restart mysql. It will recreate them and everything should work just fine and dandy again – at least well enough to dump tables and recreate.

This error can also be caused by a tmp directory with improper permissions.

Hopefully this will help someone.

This entry was posted on Thursday, May 15th, 2008 at 10:44 am PST and is filed under Servers. Find similar posts by selecting any of the following tags: . You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

No Comments

Be the first to comment on this entry.

Have your say

Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.