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

0x7f0118195700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.7/storage/innobase/btr/btr0cur.cc line 4308



    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.3.7, 10.3.12, 10.4
    • 10.6.9, 10.7.5, 10.8.4, 10.9.2


      Following error output is generated during execution of an "normal" update query and leads to a crash of mariadb master (master-master replication).
      Occurrence: 3 times on two different database tables, not reproducible so far.

      2019-01-29 13:24:41 434826568 [ERROR] InnoDB: Page old data size 15175 new data size 15391, page old max ins size 1063 new max ins size 847
      2019-01-29 13:24:41 434826568 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      2019-01-29 13:24:41 0x7f0118195700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.7/storage/innobase/btr/btr0cur.cc line 4308
      InnoDB: Failing assertion: rec
      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/xtradbinnodb-recovery-modes/
      InnoDB: about forcing recovery.
      190129 13:24:41 [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.7-MariaDB-1:10.3.7+maria~xenial-log
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 24749309 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x7efdec0009a8
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x7f0118194cf8 thread_stack 0x30000

      "Optimize table" does not help because the second crash occurred after an "optimize table run" on that database table.


        Issue Links



              marko Marko Mäkelä
              onock Christian Kueppers
              1 Vote for this issue
              11 Start watching this issue



                Git Integration

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