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

InnoDB: Assertion failure in row0sel.cc line 3961

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.5.6
    • 10.5.7
    • None
    • CentOS Linux release 7.8.2003 (Core)

    Description

      Customer hit the following assertion failure 3 times:

      2020-11-06 12:26:46 0x7f0cf417a700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.5.6/storage/innobase/row/row0sel.cc line 3961
      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.
      201106 12:26:46 [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.6-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=19
      max_threads=153
      thread_count=20
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467800 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f0ccc0009b8
      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 = 0x7f0cf4179c90 thread_stack 0x49000
      2020-11-06 12:26:46 43487 [Warning] Aborted connection 43484 to db: 'redcap' user: 'redcapsystem' host: 'xxx' (KILLED)
      2020-11-06 12:26:46 43484 [Warning] Aborted connection 43484 to db: 'redcap' user: 'redcapsystem' host: 'xxx' (This connection closed normally)
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x564dc9a840ae]
      2020-11-06 12:26:46 43488 [Warning] Aborted connection 43487 to db: 'redcap' user: 'redcapsystem' host: 'xxx' (KILLED)
      2020-11-06 12:26:46 43487 [Warning] Aborted connection 43487 to db: 'redcap' user: 'redcapsystem' host: 'xxx' (This connection closed normally)
      /usr/sbin/mariadbd(handle_fatal_signal+0x307)[0x564dc94855d7]
      /lib64/libpthread.so.0(+0xf630)[0x7f1872d76630]
      /lib64/libc.so.6(gsignal+0x37)[0x7f1870dd0387]
      :0(__GI_raise)[0x7f1870dd1a78]
      /usr/sbin/mariadbd(+0x64c5b7)[0x564dc91635b7]
      /usr/sbin/mariadbd(+0x64a45b)[0x564dc916145b]
      /usr/sbin/mariadbd(+0xd4d94c)[0x564dc986494c]
      ??:0(void std::__introsort_loop<unsigned char**, long>(unsigned char**, unsigned char**, long))[0x564dc976ed75]
      ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x564dc948bc47]
      ??:0(handler::ha_index_prev(unsigned char*))[0x564dc92c05fe]
      ??:0(sub_select(JOIN*, st_join_table*, bool))[0x564dc92b5c15]
      ??:0(JOIN::exec_inner())[0x564dc92e457f]
      ??:0(JOIN::exec())[0x564dc92e47e3]
      ??:0(mysql_select(THD*, TABLE_LIST*, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x564dc92e29a6]
      ??:0(handle_select(THD*, LEX*, select_result*, unsigned long))[0x564dc92e350c]
      /usr/sbin/mariadbd(+0x63340a)[0x564dc914a40a]
      ??:0(mysql_execute_command(THD*))[0x564dc92895d5]
      ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x564dc928c4da]
      ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x564dc928e84d]
      ??:0(do_command(THD*))[0x564dc928ffeb]
      ??:0(do_handle_one_connection(CONNECT*, bool))[0x564dc9378b02]
      ??:0(handle_one_connection)[0x564dc9378db4]
      ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x564dc96cd27d]
      2020-11-06 12:26:47 43489 [Warning] Aborted connection 43489 to db: 'redcap' user: 'redcapsystem' host: 'xxx' (This connection closed normally)
      /lib64/libpthread.so.0(+0x7ea5)[0x7f1872d6eea5]
      /lib64/libc.so.6(clone+0x6d)[0x7f1870e988dd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f0ccc025320): select v.log_view_id, r.mysql_process_id from redcap_log_view_requests r, redcap_log_view v                  where v.log_view_id = r.log_view_id and r.script_execution_time is null                  and r.ui_id = 3201 and v.ts > '2020-11-06 12:21:45' and v.session_id = 'lvvir0tcv2fe6ern7atovcln4t'                 and v.page = 'DataEntry/search.php' and r.mysql_process_id != '43486'                 order by v.log_view_id desc
      Connection ID (thread ID): 43486
      Status: KILL_CONNECTION
       
      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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=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 /dbase/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        0                    unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             256900               256900               processes 
      Max open files            35840                35840                files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       256900               256900               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: core
      
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              allen.lee@mariadb.com Allen Lee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.