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

[ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds and crashed with signal 6

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.2.27
    • N/A
    • None
    • None
    • CentOS

    Description

      server got crashed with signal 6 after [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds error.

      2021-11-05  2:45:40 140062322312960 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
      211105  2:45:40 [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.2.27-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=438
      max_threads=4002
      thread_count=455
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4826741 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 0x49000
      mysys/stacktrace.c:268(my_print_stacktrace)[0x55c9c853a2ee]
      sql/signal_handler.cc:209(handle_fatal_signal)[0x55c9c7f7bc7d]
      sigaction.c:0(__restore_rt)[0x7f921aba0630]
      :0(__GI_raise)[0x7f92199aa387]
      :0(__GI_abort)[0x7f92199aba78]
      ut/ut0ut.cc:645(ib::fatal::~fatal())[0x55c9c82816e3]
      include/sync0arr.ic:71(sync_array_get_and_reserve_cell)[0x55c9c8226d47]
      pthread_create.c:0(start_thread)[0x7f921ab98ea5]
      /lib64/libc.so.6(clone+0x6d)[0x7f9219a729fd]
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /glide/mysqld/vzdevelopment1_3400_giga/mnt/mysqld_data
      Resource Limits:
      Fatal signal 11 while backtracing
      

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              allen.lee@mariadb.com Allen Lee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.