[MDEV-11293] Hit signal 11 when excuting a procedure in which there are some DML Created: 2016-11-16  Updated: 2017-02-20  Resolved: 2017-02-20

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Procedure
Affects Version/s: 10.1.14
Fix Version/s: 10.1.22

Type: Bug Priority: Major
Reporter: Chengrui Wang Assignee: Varun Gupta (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS 6.6 x64


Attachments: Text File proc.sql    
Issue Links:
Relates
relates to MDEV-7691 Assertion `outer_context || !*from_fi... Closed
relates to MDEV-10148 Database crashes in the query to the ... Closed

 Description   

In my Mariadb 10.1.14 SERVER, when excuting a proc(see the attched file), then
I hit below signal 11 error and server crashed.

161116 16:00:54 [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.1.14-MariaDB
key_buffer_size=67108864
read_buffer_size=1048576
max_used_connections=7
max_threads=3002
thread_count=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27793441 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0x7f13c6a15008
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 = 0x7f14fbbe41d8 thread_stack 0x48400

/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0xc028ae]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x464)[0x7651f4]
/lib64/libpthread.so.0[0x3a3ae0f710]
/usr/local/mysql/bin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1c1)[0x7d4161]
/usr/local/mysql/bin/mysqld(_ZN9Item_cond10fix_fieldsEP3THDPP4Item+0x414)[0x7a2914]
/usr/local/mysql/bin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x204)[0x565ac4]
/usr/local/mysql/bin/mysqld(_ZN4JOIN7prepareEPPP4ItemP10TABLE_LISTjS1_jP8st_orderbS7_S1_S7_P13st_select_lexP18st_select_lex_unit+0x339)[0x5f24e9]
/usr/local/mysql/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xaa8)[0x607ff8]
/usr/local/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x250)[0x60b3b0]
/usr/local/mysql/bin/mysqld[0x5ac578]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x14f7)[0x5b2727]
/usr/local/mysql/bin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x89863e]
/usr/local/mysql/bin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x8c)[0x8987dc]
/usr/local/mysql/bin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x522)[0x89bb12]
/usr/local/mysql/bin/mysqld(_ZN7sp_head7executeEP3THDb+0x612)[0x89dc02]
/usr/local/mysql/bin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x623)[0x89f303]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x5c89)[0x5b6eb9]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x2b4)[0x5bab44]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x23a7)[0x5bdb77]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x2a7)[0x5bdf87]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x183)[0x68cbc3]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x42)[0x68cde2]
/usr/local/mysql/bin/mysqld[0xb04b99]
/lib64/libpthread.so.0[0x3a3ae079d1]
/lib64/libc.so.6(clone+0x6d)[0x3a3aae89dd]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f13bc6b71b0): is an invalid pointer
Connection ID (thread ID): 12
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.
161116 16:00:55 mysqld_safe Number of processes running now: 0
161116 16:00:55 mysqld_safe WSREP: not restarting wsrep node automatically
161116 16:00:55 mysqld_safe mysqld from pid file /mysqldata/3308/mysqld.pid ended



 Comments   
Comment by Elena Stepanova [ 2016-11-16 ]

We have several reports of the similar kind:
MDEV-7691
MDEV-10148
MDEV-10979 (marked as a duplicate of the previous one).
This crash is likely to be related; unfortunately, until the open ones are fixed, it's impossible to tell for sure.
I'll add this report to the collection, and I suggest you to watch the other ones as well. As soon as they get fixed, you can try the fix (maybe even before the official release, if it's easily reproducible for you), and then we'll either close the report as fixed, or, if it turns out to be different, will try to get a test case out of it, so it could be handled separately.

Comment by Chengrui Wang [ 2016-11-28 ]

Thanks, I will take notice on these related reports

Comment by Sergei Petrunia [ 2016-12-19 ]

Note: tried on 5.5, after fixes for MDEV-10148, MDEV-7691 (cset f23b41b9b8a30e0e54a1ec7a8923057b0e57e0f5). It didn't crash

However, before these fixes (cset 19896d4b3ab459d135aee6ee67cb92bce92f9b87) 5.5 doesn't crash, either.

Let's get back to this when fixes for MDEV-10148, MDEV-7691 are merged into 10.1 tree (which should be fairly soon).

Comment by Sergei Petrunia [ 2017-01-10 ]

At the moment, fixes for MDEV-10148, MDEV-7691 are in 5.5 tree only. They haven't been merged to 10.0 or 10.1. They should be merged soon.

Comment by Sergei Petrunia [ 2017-02-08 ]

... and now they are. varun, can you check if this is reproducible now? (I would try valgrind if debug doesn't reproduce). If it's reproducible, we need to start narrowing it down.

Comment by Varun Gupta (Inactive) [ 2017-02-13 ]

Not reproducible with both valgrind and debug

Comment by Varun Gupta (Inactive) [ 2017-02-20 ]

Feel free to re-open if you still manage to reproduce.

Generated at Thu Feb 08 07:48:50 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.