XMLWordPrintable

Details

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

    Description

      I upgraded yesterday mariadb from 10.5 to 10.6, and it corrupted my data.
      I had backup, so I restored and everything seemed fine, however certain queries are causing it to crash.

      Temporarily I went back to 10.5 and everything is working fine.

      I don't have much except this, because I had to restore environment as quickly as possible.

      2023-02-07 11:45:01 164 [ERROR] [FATAL] InnoDB: Unknown error Failed, retry may succeed
      230207 11:45:01 [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.6.12-MariaDB-1:10.6.12+maria~ubu2004-log source revision: 4c79e15cc3716f69c044d4287ad2160da8101cdc
      key_buffer_size=134217728                                                                                            
      read_buffer_size=131072
      max_used_connections=5
      max_threads=153
      thread_count=5
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467967 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f03c8003958
      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 = 0x7f043fed2d58 thread_stack 0x49000
      Printing to addr2line failed
      mariadbd(my_print_stacktrace+0x32)[0x555a74d3d0c2]
      mariadbd(handle_fatal_signal+0x485)[0x555a74804c55]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f0469ee0420]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f04699e400b]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f04699c3859]
      mariadbd(+0x66f1df)[0x555a744861df]
      mariadbd(+0x661815)[0x555a74478815]
      idbd(+0xdacf5d)[0x555a74bc3f5d]
      mariadbd(+0xce832d)[0x555a74aff32d]
      mariadbd(_ZN7handler18ha_index_next_sameEPhPKhj+0x275)[0x555a7480db75]
      mariadbd(+0x8041e5)[0x555a7461b1e5]
      mariadbd(_Z10sub_selectP4JOINP13st_join_tableb+0x1e5)[0x555a7460da25]
      mariadbd(+0x7e3b8c)[0x555a745fab8c]
      mariadbd(_Z10sub_selectP4JOINP13st_join_tableb+0x1a6)[0x555a7460d9e6]
      mariadbd(_ZN4JOIN10exec_innerEv+0xf67)[0x555a7463be77]
      mariadbd(_ZN4JOIN4execEv+0x39)[0x555a7463c229]
      mariadbd(_Z12mysql_selectP3THDP10TABLE_LISTR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_uni
      tP13st_select_lex+0x10a)[0x555a7463a36a]
      mariadbd(_Z13handle_selectP3THDP3LEXP13select_resultm+0x157)[0x555a7463ab27]
      mariadbd(+0x7b1581)[0x555a745c8581]
      mariadbd(_Z21mysql_execute_commandP3THDb+0x4600)[0x555a745d6bb0]
      mariadbd(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e7)[0x555a745c2f67]
      mariadbd(_Z16dispatch_command19enum_server_commandP3THDPcjb+0x10a5)[0x555a745cf635]
      mariadbd(_Z10do_commandP3THDb+0x13e)[0x555a745d173e]
      mariadbd(_Z24do_handle_one_connectionP7CONNECTb+0x3b7)[0x555a746e4727]
      mariadbd(handle_one_connection+0x5d)[0x555a746e4a7d]
      mariadbd(+0xc36766)[0x555a74a4d766]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f0469ed4609]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f0469ac0133]
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f03c8014bc0): SELECT `user_id` FROM `oc_filecache` `f` INNER JOIN `oc_mounts` `m` ON `storage_id` = `storag
      e` WHERE (`size` < 0) AND (`parent` > -1) LIMIT 1
       
      Connection ID (thread ID): 164
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_mer
      ge_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_ma
      tch_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_wi
      th_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimi
      nation=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materia
      lized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off
       
      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:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds   
      Max file size             unlimited            unlimited            bytes     
      Max data size             unlimited            unlimited            bytes     
      Max stack size            8388608              unlimited            bytes     
      Max core file size        unlimited            unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             unlimited            unlimited            processes 
      Max open files            1048576              1048576              files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       79863                79863                signals   
      Max msgqueue size         819200               819200               bytes     
      Max nice priority         0                    0                     
      Max realtime priority     0                    0                     
      Max realtime timeout      unlimited            unlimited            us        
      Core pattern: |/lib/systemd/systemd-coredump %P %u %g %s %t 9223372036854775808 %h
       
      Kernel version: Linux version 5.15.0-58-generic (buildd@lcy02-amd64-101) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, 
      GNU ld (GNU Binutils for Ubuntu) 2.38) #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023
       
      Fatal signal 11 while backtracing
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dolohow Łukasz
              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.