How to solve InnoDB: Unable to lock ./ibdata1 mysql error?

mysql linux command-line-interface innodb
Wojtek Dmyszewicz picture Wojtek Dmyszewicz · Mar 14, 2016 · Viewed 55.3k times · Source

2016-03-14 02:30:29 58150 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35 2016-03-14 02:30:29 58150 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

Answer

Wojtek Dmyszewicz picture Wojtek Dmyszewicz · Mar 14, 2016

First, list MySQL processes using the ps command:

ps aux | grep mysql

enter image description here

And then kill the process

sudo kill 56311

Related questions

error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' -- Missing /var/run/mysqld/mysqld.sock

My problem started off with me not being able to log in as root any more on my mysql install. I was attempting to run mysql without passwords turned on... but whenever I ran the command # mysqld_safe --skip-grant-tables & …

Read More
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

I am an electrical engineer who mainly plays around with power systems instead of programming. Recently, I have been following a manual to install a software suite on Ubuntu. I have no knowledge of mySQL at all, actually. I have …

Read More
How do I find the MySQL my.cnf location

Is there a MySQL command to locate the my.cnf configuration file, similar to how PHP's phpinfo() locates its php.ini?

Read More