Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.3.13
-
None
Description
2021-05-26 23:59:09 2 [ERROR] InnoDB: Page old data size 8709 new data size 8901, page old max ins size 7490 new max ins size 7298
2021-05-26 23:59:09 2 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2021-05-26 23:59:09 0x7ef54a375700 InnoDB: Assertion failure in file /mysql_log/soft/mariadb-10.3.13/storage/innobase/page/page0page.cc line 863
InnoDB: Failing assertion: cur2
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
210526 23:59:09 [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 https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.3.13-MariaDB-log
key_buffer_size=33554432
read_buffer_size=8388608
max_used_connections=388
max_threads=514
thread_count=97
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4386482 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Attachments
Issue Links
- duplicates
-
MDEV-25788 server random Crash
- Closed