Bug #39620 MySQL keep crashing got signal 11 - all data is lost
Submitted: 23 Sep 2008 22:50 Modified: 24 Oct 2008 5:47
Reporter: Moshe Sharon Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.67-community OS:Linux (CentOS 5.2 32bit)
Assigned to: CPU Architecture:Any

[23 Sep 2008 22:50] Moshe Sharon

I'm experiencing a big problem with Mysql every few days mysql server is crashing and after the database is restarting all the data is wiped away from the tables. 

I'm Using MyISAM tables on CentOS 5.2 32bit installation the MySQL version is 5.0.67 community 

this is the error I'm getting 

080923 3:50: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. 

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 393216 K 
bytes of memory 
Hope that's ok; if not, decrease some variables in the equation. 

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=0x95a8ce48, backtrace may not be correct. 
Stack range sanity check OK, backtrace follows: 
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 (nil) is invalid pointer 
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. 

Number of processes running now: 0 
080923 03:50:02 mysqld restarted 
080923 3:50:02 [Note] /usr/sbin/mysqld: ready for connections. 

More general Infromation 
I'm running the server on 2 X Quad core 2.5 MHz 
16 GB Ram 

MySQL database was moved to iscsi disks iostat output shows only 12% of disk utilization: 
sda 1.20 264.00 2.00 1005.80 54.40 10206.40 10.18 11.55 11.45 0.13 12.87 

load avg: load average: 3.52, 3.35, 3.01 

I have 1 big table with 100,000 records which updates every 1 - 5 minutes ( no inserts or deletes) and several few more tables with 50 records which also updates every few minutes. I'm using only simple SQL queries such: "update table set data1='x1', data2='x2' where id='y'" and so on. 

thanks in advance
Moshe Sharon

How to repeat:
It happens randomly
[24 Sep 2008 5:47] Sveta Smirnova
Thank you for the report.

Unfortunately not much information in the error log file. Please try debug server (mysqld-debug) and provide core file for the next time when mysqld crash. Also please send us your configuration file. Would be good also if you could provide output of top command in time when mysqld crashes.
[24 Oct 2008 23: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".