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

This article shows you what to do when MySQL 8.0.11 crashes for no reason. The content is concise and easy to understand. It will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

MySQL 8.0.11 crash logs that crash for no reason:

2018-09-04T02:01:13.313544Z 21276 [Warning] [MY-010055] [Server] IP address' 192.168.114.125' could not be resolved: Name or service not known

2018-09-04T04:57:10.808864Z 0 [Warning] [MY-010909] [Server] / usr/sbin/mysqld: Forcing close of thread 21592 user: 'BI@BL'.

2018-09-04T04:57:10.809204Z 0 [Warning] [MY-010909] [Server] / usr/sbin/mysqld: Forcing close of thread 21578 user: 'BI@BL'.

2018-09-04T04:57:10.811552Z 0 [Warning] [MY-010909] [Server] / usr/sbin/mysqld: Forcing close of thread 21242 user: 'BI@BL'.

2018-09-04T04:57:10.811681Z 0 [Warning] [MY-010909] [Server] / usr/sbin/mysqld: Forcing close of thread 21579 user: 'BI@BL'.

2018-09-04T04:57:10.815922Z 0 [Warning] [MY-010909] [Server] / usr/sbin/mysqld: Forcing close of thread 21311 user: 'BI@BL'.

2018-09-04T04:57:14.426047Z 0 [System] [MY-010910] [Server] / usr/sbin/mysqld: Shutdown complete (mysqld 8.0.11) MySQL Community Server-GPL.

2019-12-09T06:02:30.162866Z 0 [System] [MY-010116] [Server] / usr/sbin/mysqld (mysqld 8.0.11) starting as process 21276

2019-12-09T06:03:01.852081Z 0 [ERROR] [MY-000000] [InnoDB] InnoDB: Assertion failure: page0cur.cc:1182

InnoDB: thread 139750246643456

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

06:03:01 UTC-mysqld got signal 6

This could be because you hit a bug. It is also possible that this binary

Or one of the libraries it was linked against is corrupt, improperly built

Or misconfigured. This error can also be caused by malfunctioning hardware.

Attempting to collect some information that could help diagnose the problem.

As this is a crash and something is definitely wrong, the information

Collection process might fail.

The log shows that the MySQL database crashed.

Repair the crashed database.

When an abnormal restart of the MySQL service fails, you can repair the start of the MySQL service by configuring the parameter innodb_force_recovery.

Parameter innodb_force_recovery option:

1 (SRV_FORCE_IGNORE_CORRUPT): ignore checked corrupt pages. The service is forced to run even though a corrupted page is detected. Generally, you can set it to this value, and then dump exports the database table for reconstruction. 2 (SRV_FORCE_NO_BACKGROUND): blocking the running of the main thread, if the main thread needs to perform full purge operations, will result in crash. Block master thread and any purge thread from running. This value is used if crash occurs in the purge section. 3 (SRV_FORCE_NO_TRX_UNDO): no transaction rollback operation is performed. 4 (SRV_FORCE_NO_IBUF_MERGE): merge operations that insert buffers are not performed. Do not do this if it is likely to cause a crash. Do not perform statistical operations. This value may permanently corrupt the data file. If this value is used, the secondary index will be deleted and rebuilt in the future. 5 (SRV_FORCE_NO_UNDO_LOG_SCAN): without looking at the redo log, the InnoDB storage engine treats uncommitted transactions as committed. At this point, InnoDB even processes unfinished transactions as committed. This value may permanently corrupt the data file.

6 (SRV_FORCE_NO_LOG_REDO): roll forward is not performed. No redo log roll-forward is done during recovery. Make the database page in an obsolete state, which may cause more damage to the B-tree or other database structures.

Parameter innodb_force_recovery setting:

Add the parameter innodb_force_recovery to the mysqld module in the configuration file.

[mysqld]

Innodb_force_recovery = N

Then follow 1-6 to start the MySQL service.

1-5 failed, and 6 finally pulled up the database service.

After the database is started, it is in read-only mode, and the data needs to be exported and restored somewhere else.

The above is what to do when MySQL 8.0.11 crashes for no reason. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

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.