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

Maria DB Engine crashes and displays a message related to bug

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 10.4.16
    • None
    • None
    • Red Hat Enterprise Linux Server release 7.7 (Maipo)

    Description

      Our productive platform on a daily basis is suffering falls, making mention of the appearance of a bug:

      END OF INNODB MONITOR OUTPUT
      ============================
      InnoDB: ###### Diagnostic info printed to the standard error stream
      2021-11-10 16:45:51 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
      211110 16:45:51 [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.4.16-MariaDB-log
      key_buffer_size=7516192768
      read_buffer_size=67108864
      max_used_connections=12
      max_threads=1002
      thread_count=15
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 138698903 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
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5595d5d89f7e]
      /usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x5595d581b97f]
      /lib64/libpthread.so.0(+0xf630)[0x7fa0dca3b630]
      /lib64/libc.so.6(gsignal+0x37)[0x7fa0dad0c377]
      /lib64/libc.so.6(abort+0x148)[0x7fa0dad0da68]
      /usr/sbin/mysqld(+0xbc1cd0)[0x5595d5b12cd0]
      /usr/sbin/mysqld(+0xb7a2c2)[0x5595d5acb2c2]
      /lib64/libpthread.so.0(+0x7ea5)[0x7fa0dca33ea5]
      /lib64/libc.so.6(clone+0x6d)[0x7fa0dadd48cd]
      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
      Resource Limits:
      Fatal signal 11 while backtracing
      2021-11-10 16:46:01 0 [Note] mysqld: Aria engine: starting recovery
      recovered pages: 0% 12% 24% 37% 49% 62% 74% 87% 99% 100% (0.0 seconds); tables to flush: 1 0
      (0.0 seconds);
      2021-11-10 16:46:01 0 [Note] mysqld: Aria engine: recovery done
      2021-11-10 16:46:01 0 [Note] InnoDB: Using Linux native AIO
      2021-11-10 16:46:01 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2021-11-10 16:46:01 0 [Note] InnoDB: Uses event mutexes
      2021-11-10 16:46:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
      2021-11-10 16:46:01 0 [Note] InnoDB: Number of pools: 1
      2021-11-10 16:46:01 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2021-11-10 16:46:01 0 [Note] InnoDB: Initializing buffer pool, total size = 50G, instances = 50, chunk size = 128M
      2021-11-10 16:46:04 0 [Note] InnoDB: Completed initialization of buffer pool
      2021-11-10 16:46:04 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2021-11-10 16:46:04 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=16639977754157
      2021-11-10 16:46:05 0 [Note] InnoDB: Ignoring data file './DMPSTRIAD/LOGSP.ibd' with space ID 3648, since the redo log references ./DMPSTRIAD/LOGSP.ibd with space ID 3521.

      Attachments

        1. mariadb_a.err.gz
          6.38 MB
          Francisco Ortiz B.

        Issue Links

          Activity

            People

              Unassigned Unassigned
              francisco.ortiz@sonda.com Francisco Ortiz B.
              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.