[MDEV-20093] Signal 6 after insert into table Created: 2019-07-18  Updated: 2019-09-04  Resolved: 2019-09-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0.36
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Richard Stracke Assignee: Thirunarayanan Balathandayuthapani
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

CentOS Linux release 7.0.1406 (Core)
phycial server



 Description   

multiple restarts with assertion failure after insert into table

2019-07-15 18:15:55 7ff6c29c8700  InnoDB: Assertion failure in thread 140697803720448 in file pars0pars.cc line 865
InnoDB: Failing assertion: sym_node->table != NULL
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190715 18:15:55 [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.0.36-MariaDB
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=3
max_threads=1002
thread_count=4
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67870119 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7ff5d9730008
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 = 0x7ff6c29c7e60 thread_stack 0x48000
sql/item_timefunc.cc:932(Item_func_month::val_int())[0xbe1cfe]
/engn001/marsvc01/mysql/bin/mysqld(handle_fatal_signal+0x49a)[0x72855a]
sigaction.c:0(__restore_rt)[0x7ff6c26ea370]
:0(__GI_raise)[0x7ff6c15011d7]
:0(__GI_abort)[0x7ff6c15028c8]
sql/sql_class.h:876(Query_arena::alloc(unsigned long))[0x9ee942]
sql/sql_select.cc:8421(next_linear_tab)[0x9efcca]
sql/field.cc:9788(make_field(TABLE_SHARE*, unsigned char*, unsigned int, unsigned char*, unsigned char, unsigned int, enum_field_types, charset_info_st const*, Field::geometry_type, Field::utype, st_typelib*, char const*))[0xb16de1]
sql/sql_string.h:68(String)[0x9ef1da]
sql/field.cc:4974(read_bigendian)[0xb14862]
sql-common/client.c:4396(mysql_options)[0xaff3b4]
sql-common/client.c:3550(mysql_real_connect)[0xb01e80]
sql-common/client.c:3367(mysql_real_connect)[0xb020db]
sql/sql_string.cc:986(well_formed_copy_nchars(charset_info_st const*, char*, unsigned int, charset_info_st const*, char const*, unsigned int, unsigned int, char const**, char const**, char const**))[0xa16a9b]
sql/table.h:1678(operator=)[0x98616d]
/engn001/marsvc01/mysql/bin/mysqld(_ZN7handler12ha_write_rowEPh+0x100)[0x7302c0]
/engn001/marsvc01/mysql/bin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x61)[0x57fb01]
/engn001/marsvc01/mysql/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xf7f)[0x587fcf]
/engn001/marsvc01/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x6a26)[0x5a1516]
/engn001/marsvc01/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x226)[0x5a2986]
/engn001/marsvc01/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x19c7)[0x5a48d7]
/engn001/marsvc01/mysql/bin/mysqld(_Z10do_commandP3THD+0xe9)[0x5a5019]
/engn001/marsvc01/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x174)[0x673984]
/engn001/marsvc01/mysql/bin/mysqld(handle_one_connection+0x42)[0x673ac2]
/engn001/marsvc01/mysql/bin/mysqld[0x8d3969]
pthread_create.c:0(start_thread)[0x7ff6c26e2dc5]
/lib64/libc.so.6(clone+0x6d)[0x7ff6c15c373d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7ff5d1c22020): insert into tb_lm_system
[...]
Connection ID (thread ID): 5
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=off,table_elimination=on,extended_keys=on,exists_to_in=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.



 Comments   
Comment by Elena Stepanova [ 2019-07-21 ]

It would probably be a duplicate of MDEV-18654, except that the stack trace here doesn't make much sense, so assigning it to thiru to take a look.

Meanwhile, Richard, 10.0 is EOL-ed, for which versions do you expect a fix?

Comment by Thirunarayanan Balathandayuthapani [ 2019-07-24 ]

Richard Can you please attach the error log and stack trace ? It would really help us find the root cause of the issue.

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