Description:
MySQL crashed once with the following details:
121121 7:00:32 InnoDB: Assertion failure in thread 1325123904 in file ha0ha.c line 229
InnoDB: Failing assertion: struct3333
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
05:00:32 UTC - 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.
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=37
max_threads=151
thread_count=21
connection_count=21
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 461372 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7d4035]
/usr/sbin/mysqld(handle_fatal_signal+0x3e1)[0x68da41]
/lib64/libpthread.so.0[0x390920eb70]
/lib64/libc.so.6(gsignal+0x35)[0x3908630265]
/lib64/libc.so.6(abort+0x110)[0x3908631d10]
/usr/sbin/mysqld[0x8ef663]
/usr/sbin/mysqld[0x8a187e]
/usr/sbin/mysqld[0x8959f2]
/usr/sbin/mysqld[0x93dff2]
/usr/sbin/mysqld[0x93f0ab]
/usr/sbin/mysqld[0x93404c]
/usr/sbin/mysqld[0x86b734]
/usr/sbin/mysqld[0x860158]
/lib64/libpthread.so.0[0x390920673d]
/lib64/libc.so.6(clone+0x6d)[0x39086d44bd]
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.
121121 07:00:32 mysqld_safe Number of processes running now: 0
121121 07:00:32 mysqld_safe mysqld restarted
121121 7:00:33 [Warning] /usr/sbin/mysqld: ignoring option '--innodb-use-native-aio' due to invalid value 'ON'
121121 7:00:33 [Note] Plugin 'FEDERATED' is disabled.
121121 7:00:33 InnoDB: The InnoDB memory heap is disabled
121121 7:00:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121121 7:00:33 InnoDB: Compressed tables use zlib 1.2.3
121121 7:00:33 InnoDB: Using Linux native AIO
121121 7:00:33 InnoDB: Initializing buffer pool, size = 4.4G
121121 7:00:33 InnoDB: Completed initialization of buffer pool
121121 7:00:33 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 214773629863
121121 7:00:34 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 214776138383
121121 7:00:35 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 66404439, file name /mnt/db/binlog/mysql-bin.000205
121121 7:01:02 InnoDB: Waiting for the background threads to start
121121 7:01:03 InnoDB: 1.1.8 started; log sequence number 214776138383
121121 7:01:03 [Note] Recovering after a crash using /mnt/db/binlog/mysql-bin
121121 7:01:05 [Note] Starting crash recovery...
121121 7:01:05 [Note] Crash recovery finished.
How to repeat:
I don't know how to reproduce it.
Minutes earlier there was a process that inserted or updated ~15K rows, but its transaction was committed successfully a few seconds before the crash.
The tables in the database, including the tables modified by the mentions process, are not corrupted (mysqlcheck reported ok)
