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

Failing assertion: btr_page_get_prev(next_page, mtr) == btr_pcur_get_block(cursor)->page.id.page_no()



    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.3.9
    • 10.6.9, 10.7.5, 10.8.4, 10.9.2
    • Admin statements


      Hello, my name is Cassil.
      I am a new employee engineer.
      I don't know if it's okay for me to write here.
      I'm not good at English. Please excuse me.

      Our company uses mariadb.
      MariaDB is being used as a POD of k8s. Maria DB POD continues to be restarted with Error and CrashLoopBack occurring in our products.

      I don't know what the cause is. Could you please check the 'LOG' for what error this is?

      2022-02-28  7:22:06 0 [Note] mysqld (mysqld 10.3.9-MariaDB-1:10.3.9+maria~bionic) starting as process 1 ...  
      2022-02-28  7:22:06 0 [Note] InnoDB: Using Linux native AIO  2022-02-28  7:22:06 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-02-28  7:22:06 0 [Note] InnoDB: Uses event mutexes  
      2022-02-28  7:22:06 0 [Note] InnoDB: Compressed tables use zlib 1.2.11  
      2022-02-28  7:22:06 0 [Note] InnoDB: Using SSE2 crc32 instructions 
      2022-02-28  7:22:06 0 [Note] InnoDB: Initializing buffer pool, total size = 32M, instances = 1, chunk size = 32M  
      2022-02-28  7:22:06 0 [Note] InnoDB: Completed initialization of buffer pool 
      2022-02-28  7:22:06 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().  
      2022-02-28  7:22:06 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=16477207  
      2022-02-28  7:22:06 0 [Note] InnoDB: Ignoring data file './soda/build_docker_svc_temp_code.ibd' with space ID 187, since the redo log references ./soda/build_docker_svc_temp_code.ibd with space ID 186.
      2022-02-28  7:22:07 0 [Note] InnoDB: Starting final batch to recover 30 pages from redo log.
      2022-02-28  7:22:07 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-02-28  7:22:07 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-02-28  7:22:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-02-28  7:22:07 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-02-28  7:22:07 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-02-28  7:22:07 0 [Note] InnoDB: Waiting for purge to start
      2022-02-28  7:22:07 0 [Note] InnoDB: 10.3.9 started; log sequence number 16506873; transaction id 130154
      2022-02-28  7:22:07 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-02-28  7:22:07 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-02-28  7:22:07 0 [Note] Recovering after a crash using tc.log
      2022-02-28  7:22:07 0 [Note] Starting crash recovery...
      2022-02-28  7:22:07 0 [Note] Crash recovery finished.
      2022-02-28  7:22:08 0 [Note] Server socket created on IP: '::'.
      2022-02-28  7:22:08 0 [Note] Server socket created on IP: '::'.
      2022-02-28  7:22:08 0 [Note] InnoDB: Buffer pool(s) load completed at 220228  7:22:08 
      2022-02-28  7:22:08 0 [Warning] 'proxies_priv' entry '@% root@devai-service-mariadb-6b8cc7855d-kwcpc' ignored in --skip-name-resolve mode.
      2022-02-28  7:22:08 0 [Note] Reading of all Master_info entries succeded
      2022-02-28  7:22:08 0 [Note] Added new Master_info '' to hash table 
      2022-02-28  7:22:08 0 [Note] mysqld: ready for connections.Version: '10.3.9-MariaDB-1:10.3.9+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
      2022-02-28 07:23:02 0x7fd85423d700
      InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.9/storage/innobase/btr/btr0pcur.cc line 461
      InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == btr_pcur_get_block(cursor)->page.id.page_no()
      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/xtradbinnodb-recovery-modes
      InnoDB: about forcing recovery. 
      220228  7:23:02 [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 helpdiagnose the problem, but since we have already crashed,something is definitely wrong and this may fail.  Server version: 10.3.9-MariaDB-1:10.3.9+maria~bionic key_buffer_size=134217728 read_buffer_size=2097152  max_used_connections=2 max_threads=155  thread_count=8It is possible that mysqld could use up to  key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1086832 K  bytes of memory  Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fd7f4000c08  Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong...stack_bottom = 0x7fd85423cdd8 thread_stack 0x49000mysqld(my_print_stacktrace+0x2e)[0x564aa452508e]  
      mysqld(handle_fatal_signal+0x5a5)[0x564aa3fbe515] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fd85b965890]  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fd85ae74e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fd85ae76801]
      mysqld(+0x56aaf1)[0x564aa3ddfaf1]  mysqld(_Z21mysql_execute_commandP3THD+0x6132)[0x564aa3dec542]
      Trying to get some variables.Some pointers may be invalid and cause the dump to abort. 
      Query (0x7fd7f4012180): SELECT key_labels, send_dt, alert_level, total_labels,LPAD((SELECT count(*)  FROM alert_msg WHERE DATE(send_dt) = DATE(now())),3,'0') AS cnt FROM alert_msgWHERE TIMESTAMPDIFF(second, send_dt, now()) < 60 INTO OUTFILE '/var/lib/mysql/scheduled_bin/alert_msgs.csv' FIELDS TERMINATED BY '|' LINES TERMINATED BY '\n'
      Connection ID (thread ID): 48Status: 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,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
      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.  Fatal signal 11 while backtracing  

      To solve this error, what should I look at first?
      ..Do you have any idea?

      thank you


        Issue Links



              marko Marko Mäkelä
              cassil Cassilia
              0 Vote for this issue
              3 Start watching this issue



                Git Integration

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