Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5.8, 10.6.10, 10.6.12, 10.5.21, 10.5.22
-
None
Description
We had this crash on production database, but we cant see reason for this.
It was not possible to restart the server again and got error message (see picture below).
We managed to run it again by setting innodb_force_recovery=1. The server is running fine, but not knowing what caused this makes me worry
Mar 15 15:59:54 mysql02-server mariadbd: 2021-03-15 15:59:54 3535477 [Warning] Sort aborted, host: web06, user: dbuser, thread: 3535477,
|
query: SELECT * FROM `******` WHERE id = 123 ORDER BY id ASC, id ASC LIMIT 1 FOR UPDATE
|
Mar 15 15:59:54 mysql02-server mariadbd: 2021-03-15 15:59:54 0x7fc49e404700
|
InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.5.8/storage/innobase/trx/trx0trx.cc line 1336
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: We intentionally generate a memory trap.
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: If you get repeated assertion failures or crashes, even
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: immediately after the mysqld startup, there may be
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: corruption in the InnoDB tablespace. Please refer to
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
|
Mar 15 15:59:54 mysql02-server mariadbd: InnoDB: about forcing recovery.
|
Mar 15 15:59:54 mysql02-server mariadbd: 210315 15:59:54 [ERROR] mysqld got signal 6 ;
|
Mar 15 15:59:54 mysql02-server mariadbd: This could be because you hit a bug. It is also possible that this binary
|
Mar 15 15:59:54 mysql02-server mariadbd: or one of the libraries it was linked against is corrupt, improperly built,
|
Mar 15 15:59:54 mysql02-server mariadbd: or misconfigured. This error can also be caused by malfunctioning hardware.
|
Mar 15 15:59:54 mysql02-server mariadbd: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
Mar 15 15:59:54 mysql02-server mariadbd: We will try our best to scrape up some info that will hopefully help
|
Mar 15 15:59:54 mysql02-server mariadbd: diagnose the problem, but since we have already crashed,
|
Mar 15 15:59:54 mysql02-server mariadbd: something is definitely wrong and this may fail.
|
Attachments
Issue Links
- blocks
-
MDEV-24035 Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0 causing disruption and replication failure
- In Progress
- duplicates
-
MDEV-24322 Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_P REFIX/mariadb-10.5.6/storage/innobase/trx/trx0trx.cc line 1329
- Closed
- is duplicated by
-
MDEV-29478 Database Crashed with no reason
- Closed
-
MDEV-29536 InnoDB: Assertion failure
- Closed
-
MDEV-31780 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\trx\trx0trx.cc line 1252
- Closed
- relates to
-
MDEV-25296 Failing assertion: UT_LIST_GET_LEN(trx->lock.trx_locks) == 0 sporadically on SELECT with certain tables
- Closed
-
MDEV-25594 Crash in deadlock checker under high load
- Closed
-
MDEV-27031 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\trx\trx0trx.cc line 1288
- Closed
-
MDEV-31941 Assertion failures upon using OQGraph table under lock
- Confirmed
-
MDEV-32201 join_init_read_record() wrongly issues HA_ERR_OUT_OF_MEM
- Confirmed
-
MDEV-32448 MariaDB 10.6.11 - InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/trx/trx0trx.cc line 1270
- Closed