MySQL Bugs: #41048: Mysql shutdown unexpectedly (Signal 11)

Bug #41048	Mysql shutdown unexpectedly (Signal 11)
Submitted:	26 Nov 2008 10:59	Modified:	22 Feb 2009 22:23
Reporter:	Idan Shifres	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S2 (Serious)
Version:	14.12 Distrib 5.0.67	OS:	Linux (CentOS 5.2)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Hi,
I get this error codes daily:

081114 17:14:01 - mysqld got signal 11 ;
It is possible that mysqld could use up to
where mysqld died. If you see no messages after this, something went
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trac
e. Resolved
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
081114 17:14:01  mysqld restarted

I would like to know what causes the mysqld to shut itself down though it restarting itself a moment after...

Thank you.

How to repeat:
.

Thank you for the report.

Error 11 means either out of resources or bug in MySQL server. To decide what happens in your case we need more information.

Please provide full error log, configuration file and information about your hardware (CPU, RAM) for start.

My.cnf file

Attachment: my.cnf (application/octet-stream, text), 856 bytes.

The server itself is an HP DL360 G5 with 2 Quad processors 2.3Ghz and 12G Memory RAM.

The CentOS 5.2 OS is 64 bit and so is the MySQL.

We still need complete error log, with stack trace and other messages.

The full error log

Attachment: Mysql.err (text/plain), 108.31 KiB.

We are still experiencing severe problems of MySQL on this server.

We would really appreciate it if someone could inform us on how to fix or bypass this bug.

Thank you.

Thank you for the feedback.

Please provide output of SHOW CREATE TABLE customers and  SHOW TABLE STATUS LIKE 'customers'.

Show Create Table customers output

Attachment: show_create_table_customers.txt (text/plain), 6.53 KiB.

Show Table status like 'customers' output

Attachment: show_table_status.txt (text/plain), 1.37 KiB.

Thank you for the feedback.

After some testing this looks like out of resources problem for me: no crash with test data and next records in the error log:

key_buffer_size=402653184
read_buffer_size=2097152
max_used_connections=2001
max_connections=2000
...
Memory status:
Non-mmapped space allocated from system: 18472960
Number of free chunks:			 780
Number of fastbin blocks:		 0
Number of mmapped regions:		 4
Space in mmapped regions:		 436359168
Maximum total allocated space:		 0
Space available in freed fastbin blocks: 0
Total allocated space:			 9094064
Total free space:			 9378896
Top-most, releasable space:		 2230864
Estimated memory (with thread stack):    476065792

18472960/(1024*1024) = 17.6172 is more than 16G you have.

Your settings are not greedy, so nothing to tune here.

Please check system error logs next time crash happens to be sure lack of resources is the cause. Also you can schedule vmstat and log its output to gather memory usage information in time of error.

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