Bug #87462 mysqld got signal 11
Submitted: 18 Aug 2017 0:51 Modified: 18 Aug 2017 9:31
Reporter: kim kyoung youn Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.45 OS:CentOS
Assigned to: CPU Architecture:Any
Tags: like a bug

[18 Aug 2017 0:51] kim kyoung youn
Description:
The daemon prints the following log and is restarted.

170817 13:46:35 - 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=16777216

read_buffer_size=2093056

max_used_connections=32

max_connections=300

threads_connected=26

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2472781 K

bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

 

thd=0x2cf851d0

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

Cannot determine thread, fp=0x2ccd9388, backtrace may not be correct.

Stack range sanity check OK, backtrace follows:

0x8187fe0

0x81def79

0x81df14d

0x81df3e4

0x81f05bf

0x8153e5b

0x81530de

0x8153535

0x812a9f6

0x81e70da

0x81e728c

0x81e76d8

0x81f7642

0x81f996f

0x81fa2bd

0x81a2d77

0x81a9049

0x81a9611

0x81aac87

0x81ab7ca

0xb74912

0xa9f47e

New value of fp=(nil) failed sanity check, terminating stack trace!

Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved

stack trace is much more helpful in diagnosing the problem, so please do

resolve it

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort...

thd->query at 0x2cf86698  is invalid pointer

thd->thread_id=175

The manual page at http://www.mysql.com/doc/en/Crashing.html contains

information that should help you find out what is causing the crash.

What is problem?

How to repeat:
There is no special way to reproduce.
[18 Aug 2017 9:31] Miguel Solorzano
Thank you for taking the time to report a problem.  Unfortunately you
are not using a current version of the product you reported a problem
with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/.

Also, there is no test case provided in the bug report and hence there
is nothing we can verify here.  If you are able to reproduce the bug
with one of the latest versions, please attach the exact reproducible
test case and change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for your
continued support of MySQL.