
090116 15:04:32  InnoDB: Assertion failure in thread 1157658944 in file log/log0log.c line 200
InnoDB: Failing assertion: len < log->buf_size / 2
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.
090116 15:04:32 - 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=8388600
read_buffer_size=131072
max_used_connections=3
max_threads=151
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338300 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
/usr/libexec/mysqld(my_print_stacktrace+0x24) [0x945094]
/usr/libexec/mysqld(handle_segfault+0x338) [0x622138]
/lib64/libpthread.so.0 [0x320a40de70]
/lib64/libc.so.6(gsignal+0x35) [0x3208c30155]
/lib64/libc.so.6(abort+0x110) [0x3208c31bf0]
/usr/libexec/mysqld [0x811f06]
/usr/libexec/mysqld(mtr_commit+0xa2) [0x81dbd2]
/usr/libexec/mysqld [0x83dcd2]
/usr/libexec/mysqld(row_purge_step+0x991) [0x83ec41]
/usr/libexec/mysqld(que_run_threads+0x513) [0x82e273]
/usr/libexec/mysqld(trx_purge+0x30d) [0x857aed]
/usr/libexec/mysqld(srv_master_thread+0x357) [0x8515f7]
/lib64/libpthread.so.0 [0x320a4062f7]
/lib64/libc.so.6(clone+0x6d) [0x3208cd1e3d]
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.
090116 15:04:32 mysqld_safe Number of processes running now: 0
090116 15:04:32 mysqld_safe mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 1 1562621350
090116 15:04:33  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 1 1567863808
InnoDB: Doing recovery: scanned up to log sequence number 1 1573106688
InnoDB: Doing recovery: scanned up to log sequence number 1 1578349568
InnoDB: Doing recovery: scanned up to log sequence number 1 1583592448
InnoDB: Doing recovery: scanned up to log sequence number 1 1588835328
InnoDB: Doing recovery: scanned up to log sequence number 1 1594078208
InnoDB: Doing recovery: scanned up to log sequence number 1 1599321088
InnoDB: Doing recovery: scanned up to log sequence number 1 1604563968
InnoDB: Doing recovery: scanned up to log sequence number 1 1609806848
InnoDB: Doing recovery: scanned up to log sequence number 1 1615049728
InnoDB: Doing recovery: scanned up to log sequence number 1 1620292608
InnoDB: Doing recovery: scanned up to log sequence number 1 1625535488
InnoDB: Doing recovery: scanned up to log sequence number 1 1630778368
InnoDB: Doing recovery: scanned up to log sequence number 1 1636021248
InnoDB: Doing recovery: scanned up to log sequence number 1 1641264128
InnoDB: Doing recovery: scanned up to log sequence number 1 1646507008
InnoDB: Doing recovery: scanned up to log sequence number 1 1651749888
InnoDB: Doing recovery: scanned up to log sequence number 1 1656992768
InnoDB: Doing recovery: scanned up to log sequence number 1 1662235648
InnoDB: Doing recovery: scanned up to log sequence number 1 1667478528
InnoDB: Doing recovery: scanned up to log sequence number 1 1672721408
InnoDB: Doing recovery: scanned up to log sequence number 1 1677964288
InnoDB: Doing recovery: scanned up to log sequence number 1 1683207168
InnoDB: Doing recovery: scanned up to log sequence number 1 1688450048
InnoDB: Doing recovery: scanned up to log sequence number 1 1693692928
InnoDB: Doing recovery: scanned up to log sequence number 1 1698935808
InnoDB: Doing recovery: scanned up to log sequence number 1 1704178688
InnoDB: Doing recovery: scanned up to log sequence number 1 1709421568
InnoDB: Doing recovery: scanned up to log sequence number 1 1714664448
InnoDB: Doing recovery: scanned up to log sequence number 1 1714948004
090116 15:04:46  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 26315272, file name /var/lib/mysqllogs/bin-log.000652
090116 15:05:27  InnoDB: Started; log sequence number 1 1714948004
090116 15:05:27 [Note] Event Scheduler: Loaded 0 events
090116 15:05:27 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.30'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
090116 15:05:28  InnoDB: Assertion failure in thread 1157658944 in file log/log0log.c line 200
InnoDB: Failing assertion: len < log->buf_size / 2
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.
090116 15:05:28 - 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=8388600
read_buffer_size=131072
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338300 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
/usr/libexec/mysqld(my_print_stacktrace+0x24) [0x945094]
/usr/libexec/mysqld(handle_segfault+0x338) [0x622138]
/lib64/libpthread.so.0 [0x320a40de70]
/lib64/libc.so.6(gsignal+0x35) [0x3208c30155]
/lib64/libc.so.6(abort+0x110) [0x3208c31bf0]
/usr/libexec/mysqld [0x811f06]
/usr/libexec/mysqld(mtr_commit+0xa2) [0x81dbd2]
/usr/libexec/mysqld [0x83dcd2]
/usr/libexec/mysqld(row_purge_step+0x991) [0x83ec41]
/usr/libexec/mysqld(que_run_threads+0x513) [0x82e273]
/usr/libexec/mysqld(trx_purge+0x30d) [0x857aed]
/usr/libexec/mysqld(srv_master_thread+0x644) [0x8518e4]
/lib64/libpthread.so.0 [0x320a4062f7]
/lib64/libc.so.6(clone+0x6d) [0x3208cd1e3d]
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.
090116 15:05:28 mysqld_safe Number of processes running now: 0
090116 15:05:28 mysqld_safe mysqld restarted

