MySQL Bugs: #71586: mysqld got signal 11

Bug #71586	mysqld got signal 11
Submitted:	4 Feb 2014 13:33	Modified:	6 Mar 2014 17:24
Reporter:	David Leigh	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.1.54	OS:	Other (Red Hat)
Assigned to:		CPU Architecture:	Any
Tags:	clone+0x6d

Description:
Our mysqld server keeps crashing when a query is performed.   I did at first think it might be to do with query_cache_size bug, but that is set to zero as is query_cache_type.

David

How to repeat:
When a perform a query through the arcsight application

Contents of log file

[2014-02-03 07:56:24 0x7f0a61a60020-22]no more datachunks
[2014-02-03 07:56:24 0x7f0a61a60020-22]ha_arc_logger::rnd_end ...
[0x7f0a61a60020-22]Cmd:13, end ROS search, parameter:[SearchManager:11282|524299767|216834|0]
[2014-02-03 07:56:24 0x7f0a61a60020-22]datachunk opened: 321, time cost: 0 days 0 hours 0 minutes 1 seconds for query: select /* Generate Stataticstics Query for Channel name=Last Hour, channelID=QurLtf-sAABCASl2XmjoKPA==, sessionID=3s5lcbsi789eb1d03-4c9a-4b75-bd52-c4fe590ee978 */  DATE_FORMAT(event1.end_time,'%Y-%m-%d %H') "Hour(End Time)",event1.priority "Priority",count(event1.event_id) "Count(Event ID)" from  arc_event event1  where 1=1  and (event1.end_time >= '2014-01-25 22:03:32.007' and event1.end_time < '2014-01-25 23:03:32.007') and ( 1 = 1  and  1 = 1  and ((event1.session_id is null) or event1.session_id = 0)) group by DATE_FORMAT(event1.end_time,'%Y-%m-%d %H'),event1.priority
[2014-02-03 07:56:24 0x7f0a61a60020-22]rnd_next = 216835, position = 0, rnd_pos = 0
[2014-02-03 07:56:24 0x7f0a61a60020-22]eventScanCount = 216834, possible hits = 216834, matched = 0
140203  7:56:24 - 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.
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.

key_buffer_size=1073741824
read_buffer_size=262144
max_used_connections=20
max_threads=151
threads_connected=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 155712795 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3eb2d30
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 = 0x7f0b9436ec88 thread_stack 0x40000
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(my_print_stacktrace+0x26) [0x85b796]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(handle_segfault+0x33d) [0x5b19bd]
/lib64/libpthread.so.0() [0x3e4a40f500]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(thr_unlock+0x3a) [0x85fcca]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(thr_multi_unlock+0x39) [0x85fdb9]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(mysql_unlock_tables(THD*, st_mysql_lock*)+0xed) [0x5abbed]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(select_send::send_eof()+0x85) [0x59f105]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld() [0x61ece5]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(JOIN::exec()+0x1547) [0x631977]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x608) [0x632f78]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x181) [0x6332e1]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld() [0x5bc781]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(mysql_execute_command(THD*)+0x325e) [0x5c3e3e]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(Prepared_statement::execute(String*, bool)+0x312) [0x6431a2]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(Prepared_statement::execute_loop(String*, bool, unsigned char*, unsigned char*)+0x80) [0x6432c0]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(mysqld_stmt_execute(THD*, char*, unsigned int)+0x1da) [0x6436fa]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x47a) [0x5c9a7a]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(do_command(THD*)+0xde) [0x5cae8e]
/opt/arcsight/logger/current/local/mysql/libexec/mysqld(handle_one_connection+0x6ef) [0x5bb1af]
/lib64/libpthread.so.0() [0x3e4a407851]
/lib64/libc.so.6(clone+0x6d) [0x3e4a0e894d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7f0b40e0ac98 is an invalid pointer
thd->thread_id=22696
thd->killed=NOT_KILLED
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.

Thank you for the report.

But version 5.1.54 is old and version 5.1 is EOL at Dec, 31, 2013. Please upgrade to current version 5.5.36 or 5.6.16, try with it and inform us if problem still exists.

Dave 
Have they applied patch 2 and are they following best practices for what they are attempting to do?

Also remember that this is not out of the box mysql it is an update myslq for HP Arcsight CORR engine so you just cant upgrade the mysql.  It is a propriety mysql and normal mysql techniques won't always work.

Hi,

I don't really know, is there a patch, if so what are the details?   I mean it's well and truly broken!

Patch 2 has been released,may want to have the technician look to see if it will solve problem or it just may be a hardware issue.

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".