Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.7.3
-
OVH - CENTOS7
Description
Hello,
We lost the database server during the day for unkown reason.
The server started again with no problem and no data lost.
Could you please check out log below and findout the reason of this unwanted shutdown ?
Sep 6 15:27:21 ovh85 mariadbd: 2022-09-06 15:27:21 0x7ef7956b9700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.7.3/storage/innobase/trx/trx0trx.cc line 1246 |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0 |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: We intentionally generate a memory trap. |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: If you get repeated assertion failures or crashes, even |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: immediately after the mariadbd startup, there may be |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: corruption in the InnoDB tablespace. Please refer to |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/ |
Sep 6 15:27:21 ovh85 mariadbd: InnoDB: about forcing recovery. |
Sep 6 15:27:21 ovh85 mariadbd: 220906 15:27:21 [ERROR] mysqld got signal 6 ; |
Sep 6 15:27:21 ovh85 mariadbd: This could be because you hit a bug. It is also possible that this binary |
Sep 6 15:27:21 ovh85 mariadbd: or one of the libraries it was linked against is corrupt, improperly built, |
Sep 6 15:27:21 ovh85 mariadbd: or misconfigured. This error can also be caused by malfunctioning hardware. |
Sep 6 15:27:21 ovh85 mariadbd: To report this bug, see https://mariadb.com/kb/en/reporting-bugs |
Sep 6 15:27:21 ovh85 mariadbd: We will try our best to scrape up some info that will hopefully help |
Sep 6 15:27:21 ovh85 mariadbd: diagnose the problem, but since we have already crashed, |
Sep 6 15:27:21 ovh85 mariadbd: something is definitely wrong and this may fail. |
Sep 6 15:27:21 ovh85 mariadbd: Server version: 10.7.3-MariaDB-log |
Sep 6 15:27:21 ovh85 mariadbd: key_buffer_size=134217728 |
Sep 6 15:27:21 ovh85 mariadbd: read_buffer_size=131072 |
Sep 6 15:27:21 ovh85 mariadbd: max_used_connections=90 |
Sep 6 15:27:21 ovh85 mariadbd: max_threads=502 |
Sep 6 15:27:21 ovh85 mariadbd: thread_count=31 |
Sep 6 15:27:21 ovh85 mariadbd: It is possible that mysqld could use up to |
Sep 6 15:27:21 ovh85 mariadbd: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1236590 K bytes of memory |
Sep 6 15:27:21 ovh85 mariadbd: Hope that's ok; if not, decrease some variables in the equation. |
Sep 6 15:27:21 ovh85 mariadbd: Thread pointer: 0x7ef57c0008d8 |
Sep 6 15:27:21 ovh85 mariadbd: Attempting backtrace. You can use the following information to find out |
Sep 6 15:27:21 ovh85 mariadbd: where mysqld died. If you see no messages after this, something went |
Sep 6 15:27:21 ovh85 mariadbd: terribly wrong... |
Attachments
Issue Links
- duplicates
-
MDEV-24035 Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0 causing disruption and replication failure
- Confirmed
-
MDEV-25163 Rowid filter does not process storage engine error correctly.
- Closed