Skip to main content

NetApp wins prestigious Coveo Relevance Pinnacle Award. Learn more!

INSIGHT Japan :2023年 1月25日(水)ANAインターコンチネンタルホテル開催 へ参加・申込を行う

NetApp Knowledge Base

MySQL does not start in AIQUM with assertion failure due to corruption on InnoDB tablespace

Views:
222
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

ActiveIQ Unified Manager (UM) 9.6+

Issue

The MySQL service fails to start with error in the error.log of mysql

2021-02-11T23:05:51.381914Z 42 [ERROR] [MY-013183] [InnoDB] Assertion failure: rec.cc:271 thread 140576495900416
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.
23:05:51 UTC - mysqld got signal 6 ;

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device