Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-25163

Assertion failure in file trx0trx.cc

    XMLWordPrintable

    Details

      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

        1. gdb_output.txt
          135 kB
        2. image-2021-03-16-13-47-55-914.png
          image-2021-03-16-13-47-55-914.png
          278 kB
        3. mariadb_log.txt
          20 kB
        4. screenshot-1.png
          screenshot-1.png
          6 kB

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              ingig Ingi Gauti Ragnarsson
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.