版本8.0.12
問題：mysql啟動之后，馬上停止
網上資料大都是5.7的處理方法，對照方法修改 my.ini還是無法啟動。
日志：
2019-12-05T01:31:51.401656Z 0 [System] [MY-010116] [Server] D:\soft\mysql8.0.12\bin\mysqld (mysqld 8.0.12) starting as process 4864
2019-12-05T01:32:55.432782Z 0 [ERROR] [MY-000000] [InnoDB] InnoDB: Assertion failure: trx0purge.cc:165:purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: thread 5892
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.
01:32:55 UTC - mysqld got exception 0x80000003 ;
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 86998 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
轉載請註明出處，本文鏈接：https://www.uj5u.com/shujuku/36796.html
標籤：MySQL