Ubuntu下mysql无法重启

本文介绍了解决MySQL启动过程中出现的因资源暂时不可用导致的错误。通过检查是否有其他mysqld进程正在使用相同的InnoDB数据文件,并展示了如何查找并终止冲突的进程。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

错误日志:

$ tail -n 100 /var/log/mysql/error.log | head -n 20  #或者 tail -n 20 /var/log/mysql/error.log

最近的错误信息:

InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
151009 21:54:03  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
151009 21:54:03  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at

错误已经很明确了:存在其它的mysql数据库服务进程


$ ps aux | grep mysql


找到mysqld进程ID,kill

mysql     6821  0.0  1.1 484456 47276 ?        Ssl  22:15   0:00 /usr/sbin/mysqld

$ sudo kill 6821  #这里的数字是mysqld的进程ID


$ sudo /etc/init.d/mysql start

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值