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

InnoDB: Failing assertion: btr_page_get_prev(get_block->frame, mtr) == page_get_page_no(page)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 10.1.14
    • Fix Version/s: N/A
    • Labels:
      None
    • Environment:
      Server version: 10.1.14-MariaDB

      Description

      Team, MySQL is getting crashing again and again due to below error log, kindly let me know how to fix teh issues
      i have already changed innodb_force_recovery = 1, but still facing issues

      InnoDB: for more information.
      2022-10-13 14:29:27 7f212effc700 InnoDB: Assertion failure in thread 139780499162880 in file btr0cur.cc line 332
      InnoDB: Failing assertion: btr_page_get_prev(get_block->frame, mtr) == page_get_page_no(page)
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      221013 14:29:27 [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.1.14-MariaDB
      key_buffer_size=268435456
      read_buffer_size=2097152
      max_used_connections=2
      max_threads=302
      thread_count=2
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1505301 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x0
      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 0x48400
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55816a85a1be]
      /usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x55816a385f0d]
      /lib64/libpthread.so.0(+0xf100)[0x7f3b4b547100]
      /lib64/libc.so.6(gsignal+0x37)[0x7f3b4961b5f7]
      /lib64/libc.so.6(abort+0x148)[0x7f3b4961cce8]
      /usr/sbin/mysqld(+0x857953)[0x55816a62c953]
      /usr/sbin/mysqld(+0x859a5b)[0x55816a62ea5b]
      /usr/sbin/mysqld(+0x867de6)[0x55816a63cde6]
      /usr/sbin/mysqld(+0x7ee4e4)[0x55816a5c34e4]
      /usr/sbin/mysqld(+0x7f0511)[0x55816a5c5511]
      /usr/sbin/mysqld(+0x7b7167)[0x55816a58c167]
      /usr/sbin/mysqld(+0x81dcbe)[0x55816a5f2cbe]
      /usr/sbin/mysqld(+0x80bcc6)[0x55816a5e0cc6]
      /lib64/libpthread.so.0(+0x7dc5)[0x7f3b4b53fdc5]
      /lib64/libc.so.6(clone+0x6d)[0x7f3b496dc28d]
      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.
      ^C
      [root@ins0036 mysql01]$ cat /etc/my.cnf
      [mysqld_safe]
      pid-file=/var/run/mariadb/mariadb.pid

      #

      1. include all files from the config directory
        #
        #!includedir /etc/my.cnf.d
        [mysqld]
        datadir = /mnt/spool/mysql01
        tmpdir = /mnt/spool/mysql-tmp
        #tmpdir = /dev/shm/mysql-tmp
        socket = /var/lib/mysql/mysql.sock
        log_error = /var/log/mariadb/mariadb.log
        user = mysql
        skip-external-locking
        port = 3306
        max_allowed_packet = 64M
        max_connections = 300
      1. buffers and caches
        key_buffer_size = 256M
        table_cache = 4096
        sort_buffer_size = 2M
        read_buffer_size = 2M
        read_rnd_buffer_size = 8M
        join_buffer_size = 2M
        thread_cache_size = 64
        query_cache_size = 16G
        query_cache_type = 1
        query_cache_limit = 16M
        myisam_sort_buffer_size = 1M
        #optimizer_switch = 'index_condition_pushdown=off'

      #innodb
      innodb_file_per_table=1
      innodb_buffer_pool_size = 80G
      innodb_buffer_pool_instances = 64
      innodb_log_buffer_size = 8M
      innodb_log_file_size = 1G
      innodb_log_files_in_group = 2
      innodb_flush_method = O_DIRECT
      innodb_flush_log_at_trx_commit = 1
      innodb_force_recovery = 0
      innodb_fast_shutdown=0
      #innodb_purge_threads=0
      #innodb_use_native_aio = 0
      innodb-write-io-threads=16

      #innodb_lock_wait_timeout = 50
      server-id = 1

      1. MASTER
        log-bin = master-bin
        relay_log = relay-bin
        binlog-format = mixed
        sync-binlog = 1
        expire_logs_days = 3
      1. SLAVE
        #read-only = 1
        #log_bin = slave-bin
        #relay_log = relay-bin
        #binlog-format = mixed
        #sync-binlog = 1
        #expire_logs_days = 5
        #log-slave-updates = 1
        #replicate_ignore_db = cacti

      #slow_query_log
      #slow_query_log_file = /mnt/spool/mariadb/mariadb-slow.log
      #long_query_time = 2

      free -g
      total used free shared buff/cache available
      Mem: 125 2 0 2 123 120
      Swap: 1 0 1

        Attachments

          Activity

            People

            Assignee:
            danblack Daniel Black
            Reporter:
            thejaraj thejaraj
            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.