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

mysqld got signal 11

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.10, 10.9.4, 10.11.2
    • None
    • None
    • None
    • Debian 11 amd64

    Description

      The problem started after updating to 10.6.10 from 10.6.9.

      error log:

      220928  5:59:55 [ERROR] mysqld got signal 11 ;
      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.10-MariaDB-1:10.6.10+maria~deb11-log
      key_buffer_size=8589934592
      read_buffer_size=131072
      max_used_connections=34
      max_threads=1002
      thread_count=34
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 12647128 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f478c000c58
      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 = 0x7f48bcc44d58 thread_stack 0x49000
      ??:0(my_print_stacktrace)[0x55b5efee0cae]
      ??:0(handle_fatal_signal)[0x55b5ef9afeb5]
      ??:0(__restore_rt)[0x7f4be3e7a140]
      ??:0(main)[0x55b5ef69c79e]
      ??:0(main)[0x55b5ef69b5a8]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x55b5efd6c42b]
      ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x55b5efd6ec02]
      ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55b5efc9f9a5]
      ??:0(handler::ha_index_prev(unsigned char*))[0x55b5ef9b69ab]
      ??:0(report_error(TABLE*, int))[0x55b5ef7ccfb4]
      ??:0(sub_select(JOIN*, st_join_table*, bool))[0x55b5ef7bf8f5]
      ??:0(JOIN::exec_inner())[0x55b5ef7ed4e7]
      ??:0(JOIN::exec())[0x55b5ef7ed885]
      ??: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*))[0x55b5ef7eb9f6]
      ??:0(handle_select(THD*, LEX*, select_result*, unsigned long))[0x55b5ef7ec1af]
      ??:0(comp_ne_creator(bool))[0x55b5ef774ea1]
      ??:0(mysql_execute_command(THD*, bool))[0x55b5ef783be2]
      ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55b5ef785187]
      ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55b5ef787a7d]
      ??:0(do_command(THD*, bool))[0x55b5ef789748]
      ??:0(do_handle_one_connection(CONNECT*, bool))[0x55b5ef89466f]
      ??:0(handle_one_connection)[0x55b5ef8949bd]
      ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55b5efbee192]
      ??:0(start_thread)[0x7f4be3e6eea7]
      ??:0(clone)[0x7f4be3a75aef]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f478c010970): SELECT SQL_CALC_FOUND_ROWS o.`id_order`, o.`id_customer`, o.`total_paid`, o.`id_currency`, o.`date_upd`, c.`firstname`, c.`lastname`
      					FROM `ps_orders` as o
      					LEFT JOIN `ps_customer` as c ON (c.`id_customer` = o.`id_customer`)
      					WHERE `id_order` > 131328 AND o.id_shop IN (1) 
      					ORDER BY `id_order` DESC
      					LIMIT 5
       
      Connection ID (thread ID): 4474
      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,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 /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        0                    unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             514786               514786               processes 
      Max open files            1048576              1048576              files     
      Max locked memory         524288               524288               bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       514786               514786               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
       
      Kernel version: Linux version 5.10.0-18-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.140-1 (2022-09-02)
       
      2022-09-28  6:00:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-09-28  6:00:00 0 [Note] InnoDB: Number of pools: 1
      2022-09-28  6:00:00 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2022-09-28  6:00:00 0 [Note] InnoDB: Using liburing
      2022-09-28  6:00:00 0 [Note] InnoDB: Initializing buffer pool, total size = 4294967296, chunk size = 134217728
      2022-09-28  6:00:00 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-09-28  6:00:00 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=4850606667198,4850701936883
      2022-09-28  6:00:01 0 [Note] InnoDB: Starting final batch to recover 14284 pages from redo log.
      2022-09-28  6:00:02 0 [Note] InnoDB: 128 rollback segments are active.
      2022-09-28  6:00:02 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
      2022-09-28  6:00:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-09-28  6:00:02 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-09-28  6:00:02 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-09-28  6:00:02 0 [Note] InnoDB: 10.6.10 started; log sequence number 4850776853701; transaction id 3062451519
      2022-09-28  6:00:02 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-09-28  6:00:02 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-09-28  6:00:02 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
      2022-09-28  6:00:02 0 [Note] Server socket created on IP: '127.0.0.1'.
      2022-09-28  6:00:02 0 [Note] /usr/sbin/mariadbd: ready for connections.
      Version: '10.6.10-MariaDB-1:10.6.10+maria~deb11-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
      2022-09-28  6:00:02 0 [Note] InnoDB: Buffer pool(s) load completed at 220928  6:00:02
      2022-09-28  6:00:03 272 [ERROR] mariadbd: Table './livea_s_db/ps_marketplace_product_action' is marked as crashed and should be repaired
      2022-09-28  6:00:03 272 [Warning] Checking table:   './livea_s_db/ps_marketplace_product_action'
      

      With every fail one or more random tables marked as crashed and repaired. Requests are too random in fail. I tried repare and optimize all tables in all databases, but it not helped.

      Attachments

        Activity

          People

            Unassigned Unassigned
            zEvilz zEvilz
            Votes:
            0 Vote for this issue
            Watchers:
            6 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.