Bug #52623 MySQL crash
Submitted: 6 Apr 2010 16:50 Modified: 7 May 2010 7:52
Reporter: javier lopez Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.1.37-enterprise-gpl-advanced-log OS:Linux (Red Hat Enterprise Linux Server release 5.4 (Tikanga))
Assigned to: CPU Architecture:Any

[6 Apr 2010 16:50] javier lopez
MySQL crahses with following message. Process remains as zombie after that

I/O thread 0 state: waiting for i/o request (insert buffer thread)
I/O thread 1 state: waiting for i/o request (log thread)
I/O thread 2 state: waiting for i/o request (read thread)
I/O thread 3 state: waiting for i/o request (write thread)
Pending normal aio reads: 0, aio writes: 0,
 ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0
Pending flushes (fsync) log: 1; buffer pool: 1
170124233 OS file reads, 495890420 OS file writes, 367085793 OS fsyncs
0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s
Ibuf: size 9, free list len 40, seg size 50,
143669268 inserts, 143668029 merged recs, 21952970 merges
Hash table size 17393, node heap has 13 buffer(s)
0.00 hash searches/s, 0.00 non-hash searches/s
Log sequence number 91 1359132949
Log flushed up to   91 1359109391
Last checkpoint at  91 1357722380
1 pending log writes, 0 pending chkp writes
361914515 log i/o's done, 0.00 log i/o's/second
Total memory allocated 21783112; in additional pool allocated 1040640
Dictionary memory allocated 782480
Buffer pool size   512
Free buffers       0
Database pages     499
Modified db pages  299
Pending reads 0
Pending writes: LRU 106, flush list 0, single page 0
Pages read 178447655, created 2972675, written 165934487
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
No buffer pool page gets since the last printout
8 queries inside InnoDB, 12 queries in queue
11 read views open inside InnoDB
2 tablespace extents now reserved for B-tree split operations
Main thread process no. 7125, id 1185536320, state: flushing log
Number of rows inserted 186599102, updated 359834238, deleted 175548892, read 13141745208
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
100331 12:55:16  InnoDB: Assertion failure in thread 1175046464 in file srv/srv0srv.c line 2137
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
100331 12:55:16 - mysqld got signal 6 ;
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_threads = 338299 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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 = (nil) thread_stack 0x40000
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.

How to repeat:
It happend just once

Suggested fix:
Seems to be similar to bug #46628
[7 Apr 2010 7:52] Sveta Smirnova
Thank you for the report.

Please try with current version 5.1.45 and inform us if problem still exists: this can be duplicate of bug fixed after 5.1.37
[7 May 2010 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".