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

Assertion failure in file storage/innobase/log/log0log.cc line 631 (signal 6)

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5.8
    • 10.5
    • None

    Description

      2021-01-16 12:16:31 0xb3b3e0f00 InnoDB: Assertion failure in file storage/innobase/log/log0log.cc line 631
      InnoDB: Failing assertion: lsn >= log_sys.get_flushed_lsn()
      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 mysqld 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.
      210116 12:16:31 [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.5.8-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=53
      max_threads=102
      thread_count=55
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 355401 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0xb431f78d8
      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 = 0x7fffdc509f38 thread_stack 0x49000
      0x129f5ec <my_print_stacktrace+0x3c> at /usr/local/libexec/mariadbd
      0xc3911e <handle_fatal_signal+0x28e> at /usr/local/libexec/mariadbd
      0x801983b70 <_pthread_sigmask+0x530> at /lib/libthr.so.3
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0xb49110fb0): RENAME TABLE `items_prices` TO `items_prices_old`, `items_prices_new` TO `items_prices`

      Connection ID (thread ID): 1974000
      Status: NOT_KILLED

      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,i

      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.

      Attachments

        Activity

          People

            marko Marko Mäkelä
            hempalex Alexander Mikhailov
            Votes:
            2 Vote for this issue
            Watchers:
            4 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.