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

mysqld Signal 6 Shutdown Due to dict_sys.latch. in MariaDB 10.11.11

    XMLWordPrintable

Details

    • Bug
    • Status: Needs Feedback (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.11.11
    • None
    • AWS Rocky Linux release 8.10 (Green Obsidian) : 4.18.0-553.58.1.el8_10.x86_64

    Description

      Hello,

      I am currently using AWS Rocky Linux 8.10 with MariaDB version 10.11.11.
      On a server that has been running smoothly, the following call stack appears.
      Could you please let me know in what situations this might occur and how to resolve it?

      Thank you as always for your support.

      2025-09-18  0:46:27 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
      250918  0:50:43 [ERROR] /opt/dbms/engine/mariadb/bin/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: 10.11.11-MariaDB-log source revision: e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4
       
      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: 0x0
      stack_bottom = 0x0 thread_stack 0x49000
      Can't start addr2line
      /opt/dbms/engine/mariadb/bin/mariadbd(my_print_stacktrace+0x2e)[0x55bcc78dbcde]
      /opt/dbms/engine/mariadb/bin/mariadbd(handle_fatal_signal+0x22f)[0x55bcc7327eff]
      /lib64/libpthread.so.0(+0x12990)[0x7f757e9c7990]
      2025-09-18  6:22:54 0 [Note] /opt/dbms/engine/mariadb/bin/mariadbd (initiated by: unknown): Normal shutdown
      /lib64/libc.so.6(gsignal+0x10f)[0x7f757daf952f]
      2025-09-18  6:22:54 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
      250918 15:22:55 mysqld_safe mysqld from pid file /opt/dbms/data/mysql.pid ended
      

      Attachments

        Activity

          People

            marko Marko Mäkelä
            SeongGuk Kim SeongGuk Kim
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.