公司在工业区内,近日的停电导致博主这会运维的程序猿非常的崩溃,其它的都不算负担,但数据库却每天都让我心惊胆战。近日就由于停电导致服务器非正常关闭,再次来电启动时,却收到如下报错
“Starting MySQL… ERROR! The server quit without updating PID file (/home/DBs/My….pid).”
好了,MySQL无法启动了;一脸懵逼的查看错误日志,发现日志如下:
2020-05-15T06:45:55.077489Z 0 [Note] –secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2020-05-15T06:45:55.077708Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.26-log) starting as process 3244 …
2020-05-15T06:45:55.104947Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-05-15T06:45:55.105025Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-05-15T06:45:55.105048Z 0 [Note] InnoDB: Uses event mutexes
2020-05-15T06:45:55.105068Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-05-15T06:45:55.105094Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-05-15T06:45:55.105115Z 0 [Note] InnoDB: Using Linux native AIO
2020-05-15T06:45:55.106262Z 0 [Note] InnoDB: Number of pools: 1
2020-05-15T06:45:55.106710Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-05-15T06:45:55.111295Z 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-05-15T06:45:55.114935Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-05-15T06:45:55.117166Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-05-15T06:45:55.131434Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-05-15T06:45:55.132637Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 206218170 and the end 206217728.
2020-05-15T06:45:55.132678Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-05-15T06:45:55.735853Z 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
2020-05-15T06:45:55.735889Z 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2020-05-15T06:45:55.735908Z 0 [ERROR] Failed to initialize builtin plugins.
2020-05-15T06:45:55.735923Z 0 [ERROR] Aborting
2020-05-15T06:45:55.735955Z 0 [Note] Binlog end
2020-05-15T06:45:55.736998Z 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
碰上这样的问题,先备份数据库所有问题是必要的。
#cp -r MySQL MySQL_0515
翻查了无数的前辈博文,总算查到了如此的原因。原来是由于InnoDB的数据一致性校验问题导致的,而InnoDB通过啥校验的?这就不得不提ib_logfile0和ib_logfile1这些文件了,嘿嘿嘿,找到罪魁祸首了。
之后嘛,把ib_logfile0和ib_logfile1删除掉吧,先删掉再说。
再启动便好了,正常启动。没问题了…
文章评论