Bug #75694 Server keep crashing and restarting.
Submitted: 30 Jan 2015 8:06 Modified: 28 Feb 2015 15:02
Reporter: catur wibawa Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Tracing Severity:S2 (Serious)
Version:Ver 14.14 Distrib 5.5.35-ndb-7.2.15, for OS:Linux (Red Hat Enterprise Linux Server release 6.5 (Santiago))
Assigned to: CPU Architecture:Any

[30 Jan 2015 8:06] catur wibawa 
Description:
On recent 3 days our MySQL Server keep Crashing and restart it's own instance. This crash about 10 hours per day at about 10 a.m to 8 p.m every 5-10 minutes. 
When I checked the error log, it's caused by "mysqld got signal 11".
I got the stack dump for this 'hit bug', the output is:

0x82a0b5 my_print_stacktrace + 53
0x6ff054 handle_fatal_signal + 1188
0x3a4fc0f710 _end + 1318717288
0x679e58 _ZN5TABLE35mark_columns_used_by_index_no_resetEjP9st_bitmap + 56
0x7e7770 _Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyy + 3440
0x601b29 _Z21mysql_execute_commandP3THD + 12713
0x7d085e _ZN13sp_instr_stmt9exec_coreEP3THDPj + 30
0x7d09e7 _ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr + 151
0x7d5b94 _ZN13sp_instr_stmt7executeEP3THDPj + 308
0x7d3971 _ZN7sp_head7executeEP3THDb + 1729
0x7d4847 _ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE + 1703
0x600274 _Z21mysql_execute_commandP3THD + 6388
0x7d085e _ZN13sp_instr_stmt9exec_coreEP3THDPj + 30
0x7d09e7 _ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr + 151
0x7d5b94 _ZN13sp_instr_stmt7executeEP3THDPj + 308
0x7d3971 _ZN7sp_head7executeEP3THDb + 1729
0x7d4847 _ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE + 1703
0x600274 _Z21mysql_execute_commandP3THD + 6388
0x7d085e _ZN13sp_instr_stmt9exec_coreEP3THDPj + 30
0x7d09e7 _ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr + 151
0x7d5b94 _ZN13sp_instr_stmt7executeEP3THDPj + 308
0x7d3971 _ZN7sp_head7executeEP3THDb + 1729
0x7d4847 _ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE + 1703
0x600274 _Z21mysql_execute_commandP3THD + 6388
0x603558 _Z11mysql_parseP3THDPcjP12Parser_state + 392
0x6059b3 _Z16dispatch_command19enum_server_commandP3THDPcj + 7171
0x6a111f _Z24do_handle_one_connectionP3THD + 207
0x6a1221 handle_one_connection + 81
0x3a4fc079d1 _end + 1318685225
0x3a4f8e89dd _end + 1315412533

It's look like when a procedure being executed the MySQL server got bug. Is there any way to make sure what procedure is it according to the stack dump? or to make stack dump give easier to read instead of showing something like above?

Regards,

Mukhson

How to repeat:
None
[30 Jan 2015 15:02] MySQL Verification Team 
Please check against the 5.5.41 released version. If you still get the crash with this version try to provide a repeatable test case. Thanks.
[1 Mar 2015 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".