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

Mariadb crashes 11.04

    XMLWordPrintable

Details

    • Bug
    • Status: Needs Feedback (View Workflow)
    • Major
    • Resolution: Unresolved
    • 11.4.8
    • None
    • None
    • Kernel version: Linux version 6.1.86-vsh0zfs223 (root@b4ba7081eaee) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #6 SMP PREEMPT_DYNAMIC Tue Apr 16 14:52:10 UTC 2024

    Description

      Few hours after upgrade to 11.04. mariadb crashed.

      I found this report with similar error https://jira.mariadb.org/browse/MDEV-36845 but I cant find resolution or fix. Is there something to prevent it?

      Info from error log:

      2025-09-09 01:30:37 0x7f7c22ffd6c0 InnoDB: Assertion failure in file ./storage/innobase/trx/trx0purge.cc line 894
      InnoDB: Failing assertion: tail.trx_no <= last_trx_no
      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 mariadbd 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.
      250909 1:30:37 [ERROR] /usr/sbin/mariadbd got signal 6 ;
      Sorry, we probably made a mistake, and this is a bug.

      Your assistance in bug reporting will enable us to fix this for the next release.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to report
      a bug on https://jira.mariadb.org/.

      Please include the information from the server start above, to the end of the
      information below.

      Server version: 11.4.8-MariaDB-deb12-log source revision: c4ed889b74ed95fa8b4eaf96610d4c1480b346a4

      The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
      contains instructions to obtain a better version of the backtrace below.
      Following these instructions will help MariaDB developers provide a fix quicker.

      Attempting backtrace. Include this in the bug report.
      (note: Retrieving this information may fail)

      Thread pointer: 0x5572370f10e8
      stack_bottom = 0x7f7c22ffe000 thread_stack 0x30000
      2025-09-09 1:30:42 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x557233a792ce]
      /usr/sbin/mariadbd(handle_fatal_signal+0x1a3)[0x55723355bc93]
      /lib/x86_64-linux-gnu/libc.so.6(+0x3c050)[0x7fca5c6af050]
      2025-09-09 1:31:02 0 [Warning] /usr/sbin/mariadbd: Thread 2899969 (user : 'USERNAME') did not exit

      /lib/x86_64-linux-gnu/libc.so.6(+0x8aeec)[0x7fca5c6fdeec]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x12)[0x7fca5c6aefb2]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7fca5c699472]
      /usr/sbin/mariadbd(+0x6f750a)[0x55723315750a]
      /usr/sbin/mariadbd(+0x6f3f18)[0x557233153f18]
      /usr/sbin/mariadbd(+0x759543)[0x5572331b9543]
      /usr/sbin/mariadbd(+0xec2d3a)[0x557233922d3a]
      /usr/sbin/mariadbd(_ZN5tpool10task_group7executeEPNS_4taskE+0x7c)[0x557233a0e95c]
      /usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x4f)[0x557233a0d76f]
      /lib/x86_64-linux-gnu/libstdc++.so.6(+0xd44a3)[0x7fca5ca2a4a3]
      /lib/x86_64-linux-gnu/libc.so.6(+0x891f5)[0x7fca5c6fc1f5]
      /lib/x86_64-linux-gnu/libc.so.6(+0x10989c)[0x7fca5c77c89c]

      Connection ID (thread ID): 0
      Status: NOT_KILLED
      Query (0x0): (null)
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=off,sargable_casefold=on

      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits (excludes unlimited resources):
      Limit Soft Limit Hard Limit Units
      Max stack size 8388608 unlimited bytes
      Max core file size 0 unlimited bytes
      Max processes 3093728 3093728 processes
      Max open files 100000 100000 files
      Max locked memory 524288 524288 bytes
      Max pending signals 3093728 3093728 signals
      Max msgqueue size 819200 819200 bytes
      Max nice priority 0 0
      Max realtime priority 0 0
      Core pattern: core

      Kernel version: Linux version 6.1.86-vsh0zfs223 (root@b4ba7081eaee) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #6 SMP PREEMPT_DYNAMIC Tue Apr 16 14:52:10 UTC 2024

      2025-09-09 1:32:24 0 [Note] Starting MariaDB 11.4.8-MariaDB-deb12-log source revision c4ed889b74ed95fa8b4eaf96610d4c1480b346a4 server_uid aXDoHGp6qQFnH1hfeBOxYNOpVa0= as process 1986426

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              Rejchrt Jan Rejchrt
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.