InnoDB:无法锁定./ibdata1错误:35 [英] InnoDB: Unable to lock ./ibdata1 error: 35

问题描述

我正在尝试以安全模式启动MySQL，但是日志文件不断吐出:

I'm trying to start MySQL in safe mode but the log file just keeps spitting out:

[ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
[Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

注意:

1. 我已经停止了所有mysql进程，并已使用ps命令

我已经阅读了

推荐答案

可以通过运行作为MySQL发行版一部分的shell命令perror来解释来自MySQL和操作系统的奇怪错误代码.例如，在Linux上，perror 35返回OS error code 35: Resource deadlock avoided.我没有要测试的OSX系统，但是从这里开始:

Strange error codes, both from MySQL and the operating system, can be explained by running a shell command perror which is a part of MySQL distribution. On Linux, for example, perror 35 returns OS error code 35: Resource deadlock avoided. I do not have an OSX system handy to test, but from this:

http://www. opensource.apple.com/source/xnu/xnu-1456.1.26/bsd/sys/errno.h

我收集到错误35是资源暂时不可用"，这意味着某个其他进程(可能是mysqld的另一个实例?)已经锁定了该文件.

I gather that error 35 is "Resource temporarily unavailable", meaning that some other process (possibly another instance of mysqld?) has already locked the file.

要进行调试，首先，我将检查是否有另一个MySQL进程正在运行(看起来好像已经存在)，如果没有，请重新启动以确保没有奇怪的陈旧文件锁定，然后再次尝试

To debug, first I would check if there is another MySQL process running by chance (looks like you already have), and if not, reboot for good measure to make sure there are no strange stale file locks, and then try again.

某人之前曾遇到此错误，并找到了解决方法:

Somebody has run into this error before, and found a solution:

mysql_install_db，错误:35，在Mac OS X 10.9.1

这篇关于InnoDB:无法锁定./ibdata1错误:35的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！