Home > mySQL troubleshooting > Fix “InnoDB: Unable to lock ./ib_logfile0, error: 11”

Fix “InnoDB: Unable to lock ./ib_logfile0, error: 11”

February 27, 2012 Leave a comment Go to comments


1. The mySQL database hung

2. Reboot the server try to restart the mySQL database

3. After that, the mySQL database couldn’t start, and showed following errors

120226 12:23:59 [Note] Plugin ‘FEDERATED’ is disabled.

120226 12:23:59 InnoDB: The InnoDB memory heap is disabled

120226 12:23:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins

120226 12:23:59 InnoDB: Compressed tables use zlib 1.2.3

120226 12:23:59 InnoDB: Using Linux native AIO

120226 12:23:59 InnoDB: Initializing buffer pool, size = 8.0G

120226 12:23:59 InnoDB: Completed initialization of buffer pool

InnoDB: Unable to lock ./ib_logfile0, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Error in opening ./ib_logfile0

120226 12:23:59 [ERROR] Plugin ‘InnoDB’ init function returned error.

120226 12:23:59 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.

120226 12:23:59 [ERROR] Unknown/unsupported storage engine: InnoDB

120226 12:23:59 [ERROR] Aborting


Fixed Procedures

1. Go to the database directory

2. Backup the ./ib_logfile0 and copy a new one

# mv ib_logfile0 ib_logfile0.bkup

# cp -a ib_logfile0.bkup ib_logfile0

3 Restart the mySQL database

# /etc/init.d/mysql.server start


Categories: mySQL troubleshooting
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: