Shulou(Shulou.com)05/31 Report--

This article introduces how to solve the problem that mysql can not be started because of transaction log problems, the content is very detailed, interested friends can refer to, hope to be helpful to you.

The Mysql database cannot be started, as follows:

[root@testdb var] # service mysql start

Starting MySQL... ERROR! The server quit without updating PID file (/ usr/local/mysql/mysql.pid).

At first glance, it seems to be a permission problem, but a careful examination of the authority, no problem was found, so go to the error log to see

[root@testdb var] # more testdb.err2020-06-12T08:30:25.273479Z 0 [Note]-- secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled2020-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 available2020-06-12T08:30:25.286827Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins2020-06-12T08:30:25.286838Z 0 [Note] InnoDB: Uses event mutexes2020-06-12T08 30 GCC builtin 25.286845Z 0 [Note] InnoDB: GCC builtin _ atomic_thread_fence () is used for memory barrier2020-06-12T08:30:25.286852Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.112020-06-12T08:30:25.286856Z 0 [Note] InnoDB: Using Linux native AIO2020-06-12T08:30:25.288765Z 0 [Note] InnoDB: Number of pools: 12020-06-12T08:30:25.288939Z 0 [Note] InnoDB: Using CPU crc32 instructions2020-06-12T08:30 : 25.291804Z 0 [Note] InnoDB: Initializing buffer pool Total size = 4G, instances = 8, chunk size = 128M2020-06-12T08:30:25.552835Z 0 [Note] InnoDB: Completed initialization of buffer pool2020-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 setpriority (). 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 error2020-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

Check the log and find as follows:

InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 3970243421 and the end 3970243072.

The transaction log has broken files, and it is estimated that it cannot be found. Based on this, the original transaction log ib _ logfile0 and ib_logfile1 can only be renamed or deleted, and then restarted.

[root@testdb var] # service mysql startStarting MySQL...SUCCESS! This is how to solve the problem that mysql can not start because of transaction log problems. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.