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

MariaDB Frequent Crashes with mysqld got signal 11 in DsMrr_impl::close_second_handler() on INSERT

    XMLWordPrintable

Details

    • Not for Release Notes

    Description

      Hello Team,

      We have MariaDB Active-Active Master and slave DB architecture where VIP is always pointed to one writer DB at a time being on version 10.11.5.

      We have frequent crashes so attaching logs and crash dump from all three occurrences for better comparison to find the root cause to fix it

      250526  5:29:48 [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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c
      key_buffer_size=67108864
      read_buffer_size=131072
      max_used_connections=508
      max_threads=802
      thread_count=496
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f29600008e8
      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 = 0x7f2f710cbb98 thread_stack 0x49000
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5571a920312e]
      mysys/stacktrace.c:216(my_print_stacktrace)[0x5571a8cfc5b5]
      /lib64/libpthread.so.0(+0x12cf0)[0x7f55705bacf0]
      sql/multi_range_read.cc:1383(DsMrr_impl::close_second_handler())[0x5571a8c026b0]
      sql/multi_range_read.cc:1398(DsMrr_impl::dsmrr_close())[0x5571a8c027c9]
      handler/ha_innodb.cc:15770(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x5571a8fa63e7]
      sql/ha_partition.cc:9520(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x5571a8eec481]
      sql/sql_base.cc:1022(close_thread_table(THD*, TABLE**))[0x5571a8a4a7d1]
      sql/sql_base.cc:965(close_thread_tables(THD*))[0x5571a8a4aaeb]
      sql/sql_parse.cc:6097(mysql_execute_command(THD*, bool))[0x5571a8abad7f]
      sql/sql_parse.cc:8035(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x5571a8aaeb87]
      sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x5571a8ab86e6]
      sql/sql_parse.cc:1407(do_command(THD*, bool))[0x5571a8ab9dab]
      sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x5571a8bcd977]
      sql/sql_connect.cc:1318(handle_one_connection)[0x5571a8bcdcbd]
      perfschema/pfs.cc:2204(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x5571a8f03c9d]
      /lib64/libpthread.so.0(+0x81ca)[0x7f55705b01ca]
      /lib64/libc.so.6(clone+0x43)[0x7f556f900e73]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f2961e96160): Insert Into AuthenticationLog (UserIndex,UserName,NasIp,NasPort,RequestId,RadiusCode,RejectReason,PortMessage,TimeStamp,RadiusServerName,AlepoSessionId,PasswordTyped,CallerId,CalledStationId,NasPortType,ErrorCode,CustomField1,CustomField2,CustomField5,customfield3,customfield4,customnumfield1,customnumfield2,customnumfield3,customnumfield4,customnumfield5) Values(58386654,'03156200012',3414627258,3837789294,19,2,'USER REJECTED - MAC NOT MATCHED: NAS-ERROR-CODE=0, MAC-ERROR-CODE=21','Access Accept','2025-05-26 05:29:37','AAA5-ILB','HWI-PSH07283113400000c99a30AAABuv03156200012','','0c:0e:76:b8:43:b6','',13,10021,'10.140.66.18 - 1/2/5/',' - ','10.140.66.18-N1-MLK-Kot-Z-D atm 2/5:0.103','','',1,2,0,0,0)
       
      Connection ID (thread ID): 112099410
      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,hash_join_cardinality=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             2061710              2061710              processes 
      Max open files            32768                32768                files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       2061710              2061710              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: /var/coredumps/core.%e.%p
       
      Kernel version: Linux version 4.18.0-477.13.1.el8_8.x86_64 (mockbuild@x86-vm-08.build.eng.bos.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-18) (GCC)) #1 SMP Thu May 18 10:27:05 EDT 2023
       
      2025-05-26  5:35:57 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1854465
      2025-05-26  5:35:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2025-05-26  5:35:57 0 [Note] InnoDB: Number of transaction pools: 1
      2025-05-26  5:35:57 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2025-05-26  5:35:57 0 [Note] InnoDB: Using Linux native AIO
      2025-05-26  5:35:57 0 [Note] InnoDB: Initializing buffer pool, total size = 150.000GiB, chunk size = 2.344GiB
      2025-05-26  5:35:57 0 [Note] InnoDB: Completed initialization of buffer pool
      2025-05-26  5:35:58 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
      2025-05-26  5:36:00 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=61721517629855
      2025-05-26  5:36:02 0 [Note] InnoDB: End of log at LSN=61721767423998
      2025-05-26  5:36:03 0 [Note] InnoDB: 3 transaction(s) which must be rolled back or cleaned up in total 3 row operations to undo
      2025-05-26  5:36:03 0 [Note] InnoDB: Trx id counter is 163198470419
      2025-05-26  5:36:03 0 [Note] InnoDB: To recover: 147266 pages
      2025-05-26  5:36:12 0 [Note] InnoDB: Last binlog file './db2-binary.400280', position 205257714
      2025-05-26  5:36:12 0 [Note] InnoDB: 128 rollback segments are active.
      2025-05-26  5:36:12 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
      2025-05-26  5:36:12 0 [Note] InnoDB: Rolled back recovered transaction 163198315838
      2025-05-26  5:36:12 0 [Note] InnoDB: Rolled back recovered transaction 163198470410
      2025-05-26  5:36:12 0 [Note] InnoDB: Rolled back recovered transaction 163198470411
      2025-05-26  5:36:12 0 [Note] InnoDB: Rollback of non-prepared transactions completed
      2025-05-26  5:36:12 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
      2025-05-26  5:36:12 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
      2025-05-26  5:36:12 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
      2025-05-26  5:36:12 0 [Note] InnoDB: log sequence number 61721767423998; transaction id 163198470423
      2025-05-26  5:36:12 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2025-05-26  5:36:12 0 [Note] Plugin 'FEEDBACK' is disabled.
      2025-05-26  5:36:12 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
      2025-05-26  5:36:12 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
      2025-05-26  5:36:12 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
      2025-05-26  5:36:12 0 [Note] Recovering after a crash using db2-binary
      2025-05-26  5:36:12 0 [Note] Starting table crash recovery...
      2025-05-26  5:36:12 0 [Note] Crash table recovery finished.
      2025-05-26  5:36:13 0 [Note] Server socket created on IP: '0.0.0.0'.
      2025-05-26  5:36:13 0 [Note] Server socket created on IP: '::'.
      2025-05-26  5:36:13 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode.
      2025-05-26  5:36:13 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode.
      2025-05-26  5:36:13 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode.
      2025-05-26  5:36:13 3 [Note] Reading Master_info: 'master-s@002ddb3.info'  Relay_info:'relay-log-s@002ddb3.info'
      2025-05-26  5:36:13 3 [Note] Initialized Master_info from 'master-s@002ddb3.info'
      2025-05-26  5:36:13 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4
      2025-05-26  5:36:13 4 [ERROR] Master 's-db3': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
      2025-05-26  5:36:13 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master
      2025-05-26  5:36:13 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306
      2025-05-26  5:36:13 3 [Note] Started replication for 's-db3'
      2025-05-26  5:36:13 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb3.000031' position: 4
      2025-05-26  5:36:13 3 [Note] Reading Master_info: 'master-s@002ddb4.info'  Relay_info:'relay-log-s@002ddb4.info'
      2025-05-26  5:36:13 3 [Note] Initialized Master_info from 'master-s@002ddb4.info'
      2025-05-26  5:36:13 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4
      2025-05-26  5:36:13 18 [ERROR] Master 's-db4': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
      2025-05-26  5:36:13 18 [Note] Master 's-db4': Slave I/O thread killed while connecting to master
      2025-05-26  5:36:13 18 [Note] Master 's-db4': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306
      2025-05-26  5:36:13 3 [Note] Started replication for 's-db4'
      2025-05-26  5:36:13 3 [Note] Reading Master_info: 'master-s@002ddb1.info'  Relay_info:'relay-log-s@002ddb1.info'
      2025-05-26  5:36:13 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb4.000023' position: 4
      2025-05-26  5:36:13 3 [Note] Initialized Master_info from 'master-s@002ddb1.info'
      2025-05-26  5:36:13 20 [Note] Master 's-db1': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4
      2025-05-26  5:36:13 20 [ERROR] Master 's-db1': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
      2025-05-26  5:36:13 20 [Note] Master 's-db1': Slave I/O thread killed while connecting to master
      2025-05-26  5:36:13 20 [Note] Master 's-db1': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306
      2025-05-26  5:36:13 3 [Note] Started replication for 's-db1'
      2025-05-26  5:36:13 21 [Note] Master 's-db1': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb1.000030' position: 4
      2025-05-26  5:36:13 3 [Note] Reading Master_info: 'master-s@002ddb5.info'  Relay_info:'relay-log-s@002ddb5.info'
      2025-05-26  5:36:13 3 [Note] Initialized Master_info from 'master-s@002ddb5.info'
      2025-05-26  5:36:13 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4
      2025-05-26  5:36:13 22 [ERROR] Master 's-db5': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
      2025-05-26  5:36:13 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master
      2025-05-26  5:36:13 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306
      2025-05-26  5:36:13 3 [Note] Started replication for 's-db5'
      2025-05-26  5:36:13 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb5.000023' position: 4
      2025-05-26  5:36:13 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.71:3306' in log 'db1-binary.399599' at position 66121483
      2025-05-26  5:36:13 26 [Note] Slave SQL thread initialized, starting replication in log 'db1-binary.399598' at position 209489010, relay log './db2-relay.858091' position: 783
      2025-05-26  5:36:13 0 [Note] /usr/sbin/mariadbd: ready for connections.
      Version: '10.11.5-MariaDB-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
      2025-05-26  5:36:13 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.71:3306',replication started in log 'db1-binary.399599' at position 66121483
      2025-05-26  5:36:22 0 [Note] InnoDB: Buffer pool(s) load completed at 250526  5:36:22
      2025-05-26  5:37:03 2665 [Note] Start binlog_dump to slave_server(1), pos(db2-binary.400280, 205394135), using_gtid(0), gtid('')
      

      Attachments

        Issue Links

          Activity

            People

              Roel Roel Van de Paar
              ashishcyrus ashish
              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.