当前位置:论坛首页 > Linux面板 > Linux面板教程

解决强制重启系统导致mysql无法启动

发表在 Linux面板2016-12-8 10:32 [复制链接] 12 11074

SQLSTATE[HY000] [2002] No such file or directory

若您非法关机导致数据库无法启动,一般是强制关机导致MySQL二进制日志损坏,可使用以下命令处理
建议:建议关机或重启时最好先停止mysqld服务,否则有一定机率导致数据库损坏。

清理二进制日志:
  1. rm -f /www/server/data/ib_*
  2. rm -f /www/server/data/mysql-bin*
复制代码


尝试启动mysqld
  1. service mysqld start
复制代码



若还报错,请查看错误日志
  1. cat /www/server/data/*.err
复制代码



使用道具 举报 只看该作者 回复
发表于 2016-12-26 22:51:25 | 显示全部楼层
感谢,这个方法解决了我后台强制重启的问题,谢谢!
使用道具 举报 回复 支持 反对
发表于 2017-1-3 11:10:57 | 显示全部楼层
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 251 log sequence number 135630634
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 530 log sequence number 43789292
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 252 log sequence number 151634539
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 517 log sequence number 151634539
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 253 log sequence number 136982348
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 254 log sequence number 151635430
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 465 log sequence number 151635430
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 255 log sequence number 138342261
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 256 log sequence number 139028006
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 487 log sequence number 114022306
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 257 log sequence number 151636228
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 365 log sequence number 151636551
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 549 log sequence number 114022689
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 258 log sequence number 140399734
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 386 log sequence number 114023346
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 259 log sequence number 151637343
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 515 log sequence number 151637343
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 260 log sequence number 141771588
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 470 log sequence number 43772139
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 261 log sequence number 151638149
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 484 log sequence number 151638149
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 262 log sequence number 143142939
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 263 log sequence number 143829065
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 264 log sequence number 144514443
InnoDB: is in the future! Current system log sequence number 43744780.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: for more information.
170102 22:05:36 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
使用道具 举报 回复 支持 反对
发表于 2017-1-3 11:16:57 | 显示全部楼层
cjl 发表于 2016-12-26 22:51
感谢,这个方法解决了我后台强制重启的问题,谢谢!

这是Innodb数据库文件损坏引起的,可通过以下方法修复:

1、编辑MySQL配置文件
vi /etc/my.cnf
[MySQL]下添加一行:
innodbforcerecovery = 4
保存退出
2、启动MySQL
service mysqld start



使用道具 举报 回复 支持 反对
发表于 2017-1-3 11:18:10 | 显示全部楼层
吾爱互联 发表于 2017-1-3 11:10
2017-01-02 22:05:36 7f114f118720 InnoDB: Error: page 251 log sequence number 135630634
InnoDB: is in ...

这是Innodb数据库文件损坏引起的,可通过以下方法修复:

1、编辑MySQL配置文件
vi /etc/my.cnf
[MySQL]下添加一行:
innodbforcerecovery = 4
保存退出
2、启动MySQL
service mysqld start
使用道具 举报 回复 支持 反对
发表于 2017-1-3 11:34:08 | 显示全部楼层
还是不行,照做了也不行

170102 22:20:02 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
170102 22:24:09 mysqld_safe Starting mysqld daemon with databases from /www/server/data
2017-01-02 22:24:10 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-02 22:24:10 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.6.34-log) starting as process 2240 ...
2017-01-02 22:24:10 2240 [Note] Plugin 'FEDERATED' is disabled.
2017-01-02 22:24:10 2240 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-02 22:24:10 2240 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-02 22:24:10 2240 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-02 22:24:10 2240 [Note] InnoDB: Memory barrier is not used
2017-01-02 22:24:10 2240 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-02 22:24:10 2240 [Note] InnoDB: Using Linux native AIO
2017-01-02 22:24:10 2240 [Note] InnoDB: Using CPU crc32 instructions
2017-01-02 22:24:10 2240 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-02 22:24:10 2240 [Note] InnoDB: Completed initialization of buffer pool
170102 22:24:10 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
170102 22:25:01 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170102 22:25:01 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170102 22:25:02 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
2017-01-02 22:25:02 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-02 22:25:02 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.6.34-log) starting as process 3388 ...
2017-01-02 22:25:02 3388 [Note] Plugin 'FEDERATED' is disabled.
2017-01-02 22:25:02 3388 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-02 22:25:02 3388 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-02 22:25:02 3388 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-02 22:25:02 3388 [Note] InnoDB: Memory barrier is not used
2017-01-02 22:25:02 3388 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-02 22:25:02 3388 [Note] InnoDB: Using Linux native AIO
2017-01-02 22:25:02 3388 [Note] InnoDB: Using CPU crc32 instructions
2017-01-02 22:25:02 3388 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-02 22:25:02 3388 [Note] InnoDB: Completed initialization of buffer pool
2017-01-02 22:25:02 3388 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-02 22:25:02 3388 [Note] InnoDB: The log sequence numbers 43744543 and 43744543 in ibdata files do not match the log sequence number 43744780 in the ib_logfiles!
2017-01-02 22:25:02 3388 [Note] InnoDB: Database was not shutdown normally!
2017-01-02 22:25:02 3388 [Note] InnoDB: Starting crash recovery.
2017-01-02 22:25:02 3388 [Note] InnoDB: Reading tablespace information from the .ibd files...
170102 22:25:02 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
170102 22:25:05 mysqld_safe Starting mysqld daemon with databases from /www/server/data
2017-01-02 22:25:05 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-02 22:25:05 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.6.34-log) starting as process 3984 ...
2017-01-02 22:25:05 3984 [Note] Plugin 'FEDERATED' is disabled.
2017-01-02 22:25:05 3984 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-02 22:25:05 3984 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-02 22:25:05 3984 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-02 22:25:05 3984 [Note] InnoDB: Memory barrier is not used
2017-01-02 22:25:05 3984 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-02 22:25:05 3984 [Note] InnoDB: Using Linux native AIO
2017-01-02 22:25:05 3984 [Note] InnoDB: Using CPU crc32 instructions
2017-01-02 22:25:05 3984 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-02 22:25:05 3984 [Note] InnoDB: Completed initialization of buffer pool
170102 22:25:05 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
170102 22:25:10 mysqld_safe Starting mysqld daemon with databases from /www/server/data
2017-01-02 22:25:10 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-02 22:25:10 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.6.34-log) starting as process 4572 ...
2017-01-02 22:25:10 4572 [Note] Plugin 'FEDERATED' is disabled.
2017-01-02 22:25:10 4572 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-02 22:25:10 4572 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-02 22:25:10 4572 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-02 22:25:10 4572 [Note] InnoDB: Memory barrier is not used
2017-01-02 22:25:10 4572 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-02 22:25:10 4572 [Note] InnoDB: Using Linux native AIO
2017-01-02 22:25:10 4572 [Note] InnoDB: Using CPU crc32 instructions
2017-01-02 22:25:10 4572 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-02 22:25:10 4572 [Note] InnoDB: Completed initialization of buffer pool
170102 22:25:10 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
170102 22:25:13 mysqld_safe Starting mysqld daemon with databases from /www/server/data
2017-01-02 22:25:13 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-02 22:25:13 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.6.34-log) starting as process 5149 ...
2017-01-02 22:25:13 5149 [Note] Plugin 'FEDERATED' is disabled.
2017-01-02 22:25:13 5149 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-02 22:25:13 5149 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-02 22:25:13 5149 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-02 22:25:13 5149 [Note] InnoDB: Memory barrier is not used
2017-01-02 22:25:13 5149 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-02 22:25:13 5149 [Note] InnoDB: Using Linux native AIO
2017-01-02 22:25:13 5149 [Note] InnoDB: Using CPU crc32 instructions
2017-01-02 22:25:13 5149 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-02 22:25:13 5149 [Note] InnoDB: Completed initialization of buffer pool
170102 22:25:13 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
170102 22:26:32 mysqld_safe Starting mysqld daemon with databases from /www/server/data
2017-01-02 22:26:32 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-02 22:26:32 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.6.34-log) starting as process 5753 ...
2017-01-02 22:26:32 5753 [Note] Plugin 'FEDERATED' is disabled.
2017-01-02 22:26:32 5753 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-02 22:26:32 5753 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-02 22:26:32 5753 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-02 22:26:32 5753 [Note] InnoDB: Memory barrier is not used
2017-01-02 22:26:32 5753 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-02 22:26:32 5753 [Note] InnoDB: Using Linux native AIO
2017-01-02 22:26:32 5753 [Note] InnoDB: Using CPU crc32 instructions
2017-01-02 22:26:32 5753 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-02 22:26:32 5753 [Note] InnoDB: Completed initialization of buffer pool
170102 22:26:32 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
170102 22:28:12 mysqld_safe Starting mysqld daemon with databases from /www/server/data
2017-01-02 22:28:12 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-02 22:28:12 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.6.34-log) starting as process 6373 ...
2017-01-02 22:28:12 6373 [Note] Plugin 'FEDERATED' is disabled.
2017-01-02 22:28:12 6373 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-02 22:28:12 6373 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-02 22:28:12 6373 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-02 22:28:12 6373 [Note] InnoDB: Memory barrier is not used
2017-01-02 22:28:12 6373 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-02 22:28:12 6373 [Note] InnoDB: Using Linux native AIO
2017-01-02 22:28:12 6373 [Note] InnoDB: Using CPU crc32 instructions
2017-01-02 22:28:12 6373 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-02 22:28:12 6373 [Note] InnoDB: Completed initialization of buffer pool
170102 22:28:12 mysqld_safe mysqld from pid file /www/server/data/gov.cn.pid ended
使用道具 举报 回复 支持 反对
发表于 2017-1-4 10:39:55 | 显示全部楼层
宝塔开发工程师 发表于 2017-1-3 11:16
这是Innodb数据库文件损坏引起的,可通过以下方法修复:

1、编辑MySQL配置文件

添加后启动不了数据库
使用道具 举报 回复 支持 反对
发表于 2017-1-10 11:04:38 | 显示全部楼层
170108 03:53:30 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170108  3:53:30 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.47-log) starting as process 25182 ...
170108  3:53:30 InnoDB: The InnoDB memory heap is disabled
170108  3:53:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170108  3:53:30 InnoDB: Compressed tables use zlib 1.2.3
170108  3:53:30 InnoDB: Using Linux native AIO
170108  3:53:30 InnoDB: Initializing buffer pool, size = 16.0M
170108  3:53:30 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /www/server/data/ibdata1 did not exist:
InnoDB: a new database to be created!
170108  3:53:30  InnoDB: Setting file /www/server/data/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
170108  3:53:30  InnoDB: Log file /www/server/data/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
170108  3:53:30  InnoDB: Log file /www/server/data/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
170108  3:53:30  InnoDB: Waiting for the background threads to start
170108  3:53:31 InnoDB: 5.5.47 started; log sequence number 0
170108  3:53:31 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170108  3:53:31 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170108  3:53:31 [Note] Server socket created on IP: '0.0.0.0'.
170108  3:53:31 [Note] Event Scheduler: Loaded 0 events
170108  3:53:31 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170108  3:53:33 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

170108  3:53:33 [Note] Event Scheduler: Purging the queue. 0 events
170108  3:53:33  InnoDB: Starting shutdown...
170108  3:53:34  InnoDB: Shutdown completed; log sequence number 1595675
170108  3:53:34 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

170108 03:53:34 mysqld_safe mysqld from pid file /www/server/data/loca.pid ended
170108 03:53:34 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170108  3:53:34 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.47-log) starting as process 25685 ...
170108  3:53:34 [Note] Plugin 'InnoDB' is disabled.
170108  3:53:34 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170108  3:53:34 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170108  3:53:34 [Note] Server socket created on IP: '0.0.0.0'.
170108  3:53:34 [Note] Event Scheduler: Loaded 0 events
170108  3:53:34 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170108  4:03:15 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

170108  4:03:15 [Note] Event Scheduler: Purging the queue. 0 events
170108  4:03:15 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

170108 04:03:15 mysqld_safe mysqld from pid file /www/server/data/loca.pid ended
170108 04:03:16 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170108  4:03:16 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.47-log) starting as process 3077 ...
170108  4:03:16 [Note] Plugin 'InnoDB' is disabled.
170108  4:03:16 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170108  4:03:16 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170108  4:03:16 [Note] Server socket created on IP: '0.0.0.0'.
170108  4:03:16 [Note] Event Scheduler: Loaded 0 events
170108  4:03:16 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170108  4:17:30 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

170108  4:17:31 [Note] Event Scheduler: Purging the queue. 0 events
170108  4:17:31 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

170108 04:17:31 mysqld_safe mysqld from pid file /www/server/data/loca.pid ended
170108 04:17:54 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170108  4:17:54 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.47-log) starting as process 1131 ...
170108  4:17:54 [Note] Plugin 'InnoDB' is disabled.
170108  4:17:54 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170108  4:17:54 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170108  4:17:54 [Note] Server socket created on IP: '0.0.0.0'.
170108  4:17:54 [Note] Event Scheduler: Loaded 0 events
170108  4:17:54 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170109 13:41:23 [Warning] IP address '118.123.116.251' could not be resolved: Name or service not known
170109 15:20:22 [Warning] IP address '139.196.40.69' could not be resolved: Name or service not known
170109 20:28:59 [Warning] IP address '104.216.4.234' could not be resolved: Name or service not known
170110  2:58:06 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

170110  2:58:06 [Note] Event Scheduler: Purging the queue. 0 events
170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2910  user: 'tieba'

170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2903  user: 'tieba'

170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2902  user: 'tieba'

170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2901  user: 'tieba'

170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2897  user: 'tieba'

170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2885  user: 'tieba'

170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2879  user: 'tieba'

170110  2:58:08 [Warning] /www/server/mysql/bin/mysqld: Forcing close of thread 2850  user: 'tieba'

170110  2:58:08 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

170110 02:58:08 mysqld_safe mysqld from pid file /www/server/data/loca.pid ended
170110 02:58:09 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170110  2:58:09 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.47-log) starting as process 17413 ...
170110  2:58:09 [Note] Plugin 'InnoDB' is disabled.
170110  2:58:09 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170110  2:58:09 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170110  2:58:09 [Note] Server socket created on IP: '0.0.0.0'.
170110  2:58:09 [Note] Event Scheduler: Loaded 0 events
170110  2:58:09 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170110  2:59:41 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

170110  2:59:41 [Note] Event Scheduler: Purging the queue. 0 events
170110  2:59:41 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

170110 02:59:41 mysqld_safe mysqld from pid file /www/server/data/loca.pid ended
170110 02:59:43 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170110  2:59:43 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.47-log) starting as process 18039 ...
170110  2:59:43 [Note] Plugin 'InnoDB' is disabled.
170110  2:59:43 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170110  2:59:43 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170110  2:59:43 [Note] Server socket created on IP: '0.0.0.0'.
170110  2:59:43 [Note] Event Scheduler: Loaded 0 events
170110  2:59:43 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170110 03:00:20 mysqld_safe A mysqld process already exists
使用道具 举报 回复 支持 反对
发表于 2017-1-13 10:20:13 | 显示全部楼层
kiffaater 发表于 2017-1-10 11:04
170108 03:53:30 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170108  3:53 ...

已存在mysqld进程,pkill -9 mysqld 然后重启服务器即可
使用道具 举报 回复 支持 反对
发表于 2017-2-8 09:03:16 | 显示全部楼层
宝塔开发工程师 发表于 2017-1-3 11:16
这是Innodb数据库文件损坏引起的,可通过以下方法修复:

1、编辑MySQL配置文件

根据你的修复方法,现在数据库出错。
使用道具 举报 回复 支持 反对
发表于 2017-2-16 11:03:50 | 显示全部楼层
170216 11:00:23 [Note] Plugin 'FEDERATED' is disabled.
170216 11:00:23 InnoDB: The InnoDB memory heap is disabled
170216 11:00:23 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170216 11:00:23 InnoDB: Compressed tables use zlib 1.2.3
170216 11:00:23 InnoDB: Initializing buffer pool, size = 128.0M
170216 11:00:23 InnoDB: Completed initialization of buffer pool
170216 11:02:18 [Note] Plugin 'FEDERATED' is disabled.
170216 11:02:18 InnoDB: The InnoDB memory heap is disabled
170216 11:02:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170216 11:02:18 InnoDB: Compressed tables use zlib 1.2.3
170216 11:02:18 InnoDB: Initializing buffer pool, size = 128.0M
170216 11:02:18 InnoDB: Completed initialization of buffer pool
使用道具 举报 回复 支持 反对
发表于 2017-5-31 11:54:30 | 显示全部楼层
求解这是什么意思
cs.png
使用道具 举报 回复 支持 反对
发表于 2018-11-13 18:49:40 | 显示全部楼层
感谢良哥,完全解决!
使用道具 举报 回复 支持 反对
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

快速回复 返回顶部 返回列表