如何解决mysql因为事务日志问题不能启动的问题
发布时间：2022-01-17 13:53:18 所属栏目：MySql教程 来源：互联网
导读：这篇文章给大家介绍如何解决mysql因为事务日志问题无法启动的问题，内容非常详细，感兴趣的小伙伴们可以参考借鉴，希望对大家能有所帮助。 Mysql数据库无法启动，具体如下： [root@testdb var]#service mysql start Starting MySQL... ERROR! The server qui
|
这篇文章给大家介绍如何解决mysql因为事务日志问题无法启动的问题，内容非常详细，感兴趣的小伙伴们可以参考借鉴，希望对大家能有所帮助。 Mysql数据库无法启动，具体如下： [root@testdb var]#service mysql start Starting MySQL... ERROR! The server quit without updating PID file (/usr/local/mysql/mysql.pid). 初看，好像是权限问题，但仔细检查权限，没有发现问题，所以进入错误日志看 [root@testdb var]# more testdb.err 2020-06-12T08:30:25.273479Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled 2020-06-12T08:30:25.273850Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.26-log) starting as process 10090 ... 2020-06-12T08:30:25.286777Z 0 [Note] InnoDB: PUNCH HOLE support available 2020-06-12T08:30:25.286827Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-06-12T08:30:25.286838Z 0 [Note] InnoDB: Uses event mutexes 2020-06-12T08:30:25.286845Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2020-06-12T08:30:25.286852Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-06-12T08:30:25.286856Z 0 [Note] InnoDB: Using Linux native AIO 2020-06-12T08:30:25.288765Z 0 [Note] InnoDB: Number of pools: 1 2020-06-12T08:30:25.288939Z 0 [Note] InnoDB: Using CPU crc32 instructions 2020-06-12T08:30:25.291804Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M 2020-06-12T08:30:25.552835Z 0 [Note] InnoDB: Completed initialization of buffer pool 2020-06-12T08:30:25.589770Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of se tpriority(). 2020-06-12T08:30:25.603855Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2020-06-12T08:30:25.627920Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 3970243421 and the end 3970243072. 2020-06-12T08:30:25.627962Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2020-06-12T08:30:26.229118Z 0 [ERROR] Plugin 'InnoDB' init function returned error. 2020-06-12T08:30:26.229160Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2020-06-12T08:30:26.229168Z 0 [ERROR] Failed to initialize builtin plugins. 2020-06-12T08:30:26.229172Z 0 [ERROR] Aborting 查看日志，发现如下： InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 3970243421 and the end 3970243072. 事务日志有断档，估计也找不出来了，基于此，只能把原来的事务日志ib_logfile0和ib_logfile1重命名或者删除掉，然后再重新启动 [root@testdb var]#service mysql start Starting MySQL...SUCCESS! 关于如何解决mysql因为事务日志问题无法启动的问题就分享到这里了，希望以上内容可以对大家有一定的帮助，可以学到更多知识。如果觉得文章不错，可以把它分享出去让更多的人看到。 （编辑：91站长网） 【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容! |
