在2021-01-11，MySQL8.0.18版本出现未知错误导致服务宕机。InnoDB模块出现断言失败，提示可能的数据表空间损坏。建议参照官方文档进行强制恢复并提交详细bug报告。
2021-01-11T10:42:12.413442+08:00 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: row0pread.cc:727:!page_cur_is_after_last(&page_cursor) thread 139896966547200
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.
02:42:12 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, someth
最低0.47元/天 解锁文章
扫一扫
1972
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
