我有一个简单的网络服务器(Debian 6.0 x86,1 GB 内存和 10 GB 可用空间的 DirectAdmin,mySQl 版本 5.5.9),但是 mySQL 服务器不断崩溃,我需要杀死所有 mySQL 进程才能重新启动它再次。
/var/log/mysql-error.log 输出:
130210 21:04:26 InnoDB: Using Linux native AIO
130210 21:04:34 InnoDB: Initializing buffer pool, size = 128.0M
130210 21:05:42 InnoDB: Completed initialization of buffer pool
130210 21:05:48 InnoDB: Initializing buffer pool, size = 128.0M
130210 21:06:22 InnoDB: Initializing buffer pool, size = 128.0M
130210 21:06:27 mysqld_safe mysqld from pid file /usr/local/mysql/data/website.pid ended
130210 21:06:29 mysqld_safe mysqld from pid file /usr/local/mysql/data/website.pid ended
130210 21:07:22 InnoDB: Completed initialization of buffer pool
130210 21:07:51 mysqld_safe mysqld from pid file /usr/local/mysql/data/website.pid ended
130210 21:08:33 InnoDB: Completed initialization of buffer pool
130210 21:12:03 [Note] Plugin 'FEDERATED' is disabled.
130210 21:12:47 InnoDB: The InnoDB memory heap is disabled
130210 21:12:47 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
130210 21:12:47 InnoDB: Compressed tables use zlib 1.2.3
130210 21:12:47 InnoDB: Using Linux native AIO
130210 21:13:11 InnoDB: highest supported file format is Barracuda.
130210 21:13:23 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130210 21:14:05 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
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.
130210 21:17:53 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
130210 21:17:53 InnoDB: Operating system error number 11 in a file operation.
Run Code Online (Sandbox Code Playgroud)
我在这里的 mySQL 网站上找到了一个主题,但是没有解决方案。
任何人的想法?
小智 42
来自同一博客中一个评论的另一种方法:
这对我有帮助:
lsof -i:3306
然后杀死它(进程号)
杀死 -9 进程
例如 kill -9 13498
然后再次尝试重新启动 MySQL。
通过http://www.webhostingtalk.com/archive/index.php/t-1070293.html
小智 30
使用 Ubuntu 14.04。当我尝试通过以下方式重新启动时遇到此问题
/etc/init.d/mysql restart
Run Code Online (Sandbox Code Playgroud)
而是尝试
service mysql restart
Run Code Online (Sandbox Code Playgroud)
小智 23
解决方案
复制原始文件(ibdata1、ib_logfile0、ib_logfile1...)。
mv ibdata1 ibdata1.bak
cp -a ibdata1.bak ibdata1
Run Code Online (Sandbox Code Playgroud)
http://cglreport.zhenhua.info/2008/08/mysql-error-unable-to-lock-ibdata1.html
Mic*_*ton 22
此问题的最常见原因是尝试在 MySQL 已经运行时启动它。
要解决它,请关闭所有正在运行的 MySQL 实例,然后使用正常的启动脚本重新启动它,例如service mysql start.
在使用分发包版本时不要尝试手动启动 MySQL,除非您准备好迎接伤害。
这帮助我解决了它:
删除所有 ibdata 文件,让 mysql 创建它们。
停止mysql:
service mysql stop
Run Code Online (Sandbox Code Playgroud)
转到mysql库:
cd /var/lib/mysql/
Run Code Online (Sandbox Code Playgroud)
将 innodb 文件移动到某个地方以备不时之需:
mv ib* /root/
Run Code Online (Sandbox Code Playgroud)
启动mysql:
service mysql start
Run Code Online (Sandbox Code Playgroud)
| 归档时间: |
|
| 查看次数: |
198057 次 |
| 最近记录: |