MySQL Bugs: #67284: mysqld got signal 11 and we off the "myisam_use

Bug #67284	mysqld got signal 11 and we off the "myisam_use_mmap"
Submitted:	18 Oct 2012 8:04	Modified:	29 Dec 2012 21:53
Reporter:	Deng Han	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.5.14	OS:	Linux (RHEL 5.6)
Assigned to:		CPU Architecture:	Any
Tags:	5.5.14, Signal 11

Description:
We use two mysql server for Master-Master mode.
This afternoon, We found that error occurred and synchronization failure on one server, check the other server's log and found the "mysqld got signal 11".

Error content:
________________________________________________________________________
121018  9:00:01 - 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=67108864
read_buffer_size=131072
max_used_connections=43
max_threads=1000
thread_count=24
connection_count=24
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2252918 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2aaef43e6170
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 = 0x5983f0e8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x797f89]
/usr/sbin/mysqld(handle_segfault+0x380)[0x4fdaa0]
/lib64/libpthread.so.0[0x3b0620eb10]
[0x2aaee82d7f00]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2aaee0206640): is an invalid pointer
Connection ID (thread ID): 156905
Status: NOT_KILLED
_______________________________________________________________

We search the reason and http://bugs.mysql.com/bug.php?id=48726 have the similar problem, but we off the "myisam_use_mmap" engine.

How to repeat:
N/A

my.cnf

Attachment: my.txt (text/plain), 5.94 KiB.

We will need a proper stack trace (from gdb, or from a corefile).
But, it's likely a bug is fixed since 5.5.14.

Can you please use a modern version, such as 5.5.28 and check how it fares?

Ok, We'd prefer to observe the MySQL server a period of time, if there is a similar error occurs, we will consider upgrading the version of MySQL.

Hi,

Can you give me a bug report or root cause about the "mysqld got signal 11"?
Thus, I would get the reason to upgrade mysql version.

B.R
Deng Han

Nope, we can't tell anything.  Provide us the stack trace from a crash, and we might be able to say something.

Thank you for the feedback.

"mysqld got signal 11" usually means MySQL server got reject from the operating system for a resource requests, most often memory. There can be hundreds of reasons for this error from lack of resource on your machine, improper configuration to MySQL bug. This is why we need core file or stack trace from you.

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