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

[ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 10.6.7
    • Fix Version/s: N/A
    • Component/s: None
    • Labels:
      None

      Description

      Similar to MDEV-27026 but still in 10.6.7.
      No core dump available.

      2022-09-28  1:32:37 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/
      220928  1:32:37 [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.6.7-MariaDB-1:10.6.7+maria~buster-log
      key_buffer_size=16777216
      read_buffer_size=131072
      max_used_connections=130
      max_threads=282
      thread_count=131
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 637332 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      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 = 0x0 thread_stack 0x30000
      mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.7/tpool/task_group.cc:86: tpool::task_group::~task_group(): Assertion `m_queue.empty()' failed.
      Printing to addr2line failed
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55ecb25bd36e]
      /usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x55ecb20897b5]
      mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.7/tpool/task_group.cc:86: tpool::task_group::~task_group(): Assertion `m_queue.empty()' failed.
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fbfd459f730]
      mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.7/tpool/task_group.cc:86: tpool::task_group::~task_group(): Assertion `m_queue.empty()' failed.
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7fbfd40f67bb]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7fbfd40e1535]
      mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.7/tpool/task_group.cc:86: tpool::task_group::~task_group(): Assertion `m_queue.empty()' failed.
      /usr/sbin/mariadbd(+0x651ec7)[0x55ecb1d43ec7]
      /usr/sbin/mariadbd(+0x64a105)[0x55ecb1d3c105]
      /usr/sbin/mariadbd(tpool::thread_pool_generic::timer_generic::execute(void*)+0x35)[0x55ecb25516b5]
      /usr/sbin/mariadbd(tpool::task::execute()+0x2b)[0x55ecb25525eb]
      /usr/sbin/mariadbd(tpool::thread_pool_generic::worker_main(tpool::worker_data*)+0x4f)[0x55ecb25511ff]
      mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.7/tpool/task_group.cc:86: tpool::task_group::~task_group(): Assertion `m_queue.empty()' failed.
      /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xbbb2f)[0x7fbfd44bfb2f]
      mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.7/tpool/task_group.cc:86: tpool::task_group::~task_group(): Assertion `m_queue.empty()' failed.
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7fbfd4594fa3]
      mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.7/tpool/task_group.cc:86: tpool::task_group::~task_group(): Assertion `m_queue.empty()' failed.
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fbfd41b7eff]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /var/lib/mysql
      
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              claudio.nanni Claudio Nanni
              Reporter:
              claudio.nanni Claudio Nanni
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

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