2022-05-06 16:25:11 0x7f728d7fa700 InnoDB: Assertion failure in file /builddir/build/BUILD/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 313
InnoDB: Failing assertion: btr_page_get_next(latch_leaves.blocks[0]->frame) == page_get_page_no(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to System Dashboard - Jira
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: InnoDB Recovery Modes
InnoDB: about forcing recovery.
220506 16:25:11 [ERROR] 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.
To report this bug, see MariaDB Community Bug Reporting
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
When i try to use recovery mode 3 it was getting started
How to do the recovery ?
Even I'm unable to dump in recovery mode 6
mysqldump -AER > /root/recovery_dump.sql
mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `wpnm_options` at row: 374
InnoDB: Failing assertion: btr_page_get_next(latch_leaves.blocks[0]->frame) == page_get_page_no(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to System Dashboard - Jira
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: InnoDB Recovery Modes
InnoDB: about forcing recovery.
220506 16:25:11 [ERROR] 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.
To report this bug, see MariaDB Community Bug Reporting
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
When i try to use recovery mode 3 it was getting started
How to do the recovery ?
Even I'm unable to dump in recovery mode 6
mysqldump -AER > /root/recovery_dump.sql
mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `wpnm_options` at row: 374
Last edited by a moderator: