[MDEV-19967] signal 6 with wrong page size during btr_page_reorganize Created: 2019-07-05  Updated: 2023-04-11  Resolved: 2023-04-11

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.4.6
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Richard Stracke Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS 7.6 64Bit
Virtualized, On Premise



 Description   

Galera cluster, all nodes crashed on start with

2019-07-05 11:07:39 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.4.6-MariaDB-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2019-07-05 11:07:39 22 [ERROR] InnoDB: Page old data size 10975 new data size 10991, page old max ins size 5255 new max ins size 5239
2019-07-05 11:07:39 22 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2019-07-05 11:07:39 0x7f44ec0d9700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.6/storage/innobase/btr/btr0cur.cc line 4685
InnoDB: Failing assertion: rec
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.
190705 11:07:39 [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.4.6-MariaDB-log
key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=3
max_threads=502
thread_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1137421 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f414c0009a8
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 = 0x7f44ec0d8cf0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55909a433d7e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x559099ec67af]
sigaction.c:0(__restore_rt)[0x7f44f26ac5d0]
:0(__GI_raise)[0x7f44f097f207]
:0(__GI_abort)[0x7f44f09808f8]
/usr/sbin/mysqld(+0x59948a)[0x559099bc648a]
/usr/sbin/mysqld(+0xbab868)[0x55909a1d8868]
/usr/sbin/mysqld(+0xb325c3)[0x55909a15f5c3]
/usr/sbin/mysqld(+0xb376c9)[0x55909a1646c9]
/usr/sbin/mysqld(+0xb382b4)[0x55909a1652b4]
/usr/sbin/mysqld(+0xb0f34b)[0x55909a13c34b]
/usr/sbin/mysqld(+0xa46532)[0x55909a073532]
/usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhS1_+0x377)[0x559099ed2937]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x7df)[0x559099c8a9cf]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1100)[0x559099c90b70]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3f32)[0x559099cbfad2]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x24b)[0x559099cc514b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1b66)[0x559099cc7ed6]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x11c)[0x559099cc94ac]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x21a)[0x559099da4d6a]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x559099da4ecd]
pthread_create.c:0(start_thread)[0x7f44f26a4dd5]
/lib64/libc.so.6(clone+0x6d)[0x7f44f0a46ead]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f414c00fd70): insert into  [....]
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
 
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.
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             256935               256935               processes
Max open files            16364                16364                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       256935               256935               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



 Comments   
Comment by Oren Bissick (Inactive) [ 2019-07-16 ]

Getting similar error.

2019-07-15 16:31:41 0x7f10c9dcc700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.6/storage/innobase/rem/rem0rec.cc line 859
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.
190715 16:31:41 [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.4.6-MariaDB
key_buffer_size=52428800
read_buffer_size=131072
max_used_connections=163
max_threads=153
thread_count=29
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4703300 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f100801fc88
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 = 0x7f10c9dcbcc0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56108a832d7e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x56108a2c57af]
/lib64/libpthread.so.0(+0xf5d0)[0x7f15e09ba5d0]
/lib64/libc.so.6(gsignal+0x37)[0x7f15dec8d207]
/lib64/libc.so.6(abort+0x148)[0x7f15dec8e8f8]
/usr/sbin/mysqld(+0x59948a)[0x561089fc548a]
/usr/sbin/mysqld(+0xae18f3)[0x56108a50d8f3]
/usr/sbin/mysqld(+0xabeb45)[0x56108a4eab45]
/usr/sbin/mysqld(+0xbb14b3)[0x56108a5dd4b3]
/usr/sbin/mysqld(+0xafa11f)[0x56108a52611f]
/usr/sbin/mysqld(+0xafbe71)[0x56108a527e71]
/usr/sbin/mysqld(+0xafe118)[0x56108a52a118]
/usr/sbin/mysqld(+0xb0e03d)[0x56108a53a03d]
/usr/sbin/mysqld(+0xa4ed35)[0x56108a47ad35]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x320)[0x56108a2d1570]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6a)[0x56108a08925a]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1100)[0x56108a08fb70]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3f32)[0x56108a0bead2]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x24b)[0x56108a0c414b]
/usr/sbin/mysqld(+0x6989f9)[0x56108a0c49f9]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x298f)[0x56108a0c7cff]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x11c)[0x56108a0c84ac]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x21a)[0x56108a1a3d6a]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x56108a1a3ecd]
/usr/sbin/mysqld(+0xdb88bd)[0x56108a7e48bd]
/lib64/libpthread.so.0(+0x7dd5)[0x7f15e09b2dd5]
/lib64/libc.so.6(clone+0x6d)[0x7f15ded54ead]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f1008016fa0): is an invalid pointer
Connection ID (thread ID): 881546
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
 
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.
 
We think the query pointer is invalid, but we will try to print it anyway. 
Query: INSERT INTO ....
 
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             127868               127868               processes 
Max open files            14190                14190                files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       127868               127868               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

Comment by Jan Lindström (Inactive) [ 2021-10-06 ]

To even start analyze I would need stack trace where all symbols are resolved either by opening the core file or by using debug package symbols.

Comment by Elena Stepanova [ 2021-11-03 ]

There is a resolved stack trace for a similar failure in MDEV-18519.

Generated at Thu Feb 08 08:55:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.