MySQL crashing during startup


I just had a server on which I was not able to start MySQL.

The MySQL error log shows the following:

121121 18:30:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121121 18:30:13 [Note] Plugin ‘FEDERATED’ is disabled.
121121 18:30:13  InnoDB: Initializing buffer pool, size = 8.0M
121121 18:30:13  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 4 420487967
121121 18:30:13  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 4 420585640
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1156938 row operations to undo
InnoDB: Trx id counter is 0 303173632
121121 18:30:14  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 17:30:14 UTC – 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.

key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338374 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x86c1ee]
/usr/sbin/mysqld(handle_fatal_signal+0x380)[0x6bef70]
/lib64/libpthread.so.0[0x3d8640ebe0]
/usr/sbin/mysqld(page_cur_insert_rec_low+0x335)[0x7bc345]
/usr/sbin/mysqld(page_cur_parse_insert_rec+0x2dc)[0x7bce2c]
/usr/sbin/mysqld[0x7aad64]
/usr/sbin/mysqld(recv_recover_page+0x36b)[0x7ac9db]
/usr/sbin/mysqld(buf_page_io_complete+0x55b)[0x769e9b]
/usr/sbin/mysqld(fil_aio_wait+0x139)[0x784669]
/usr/sbin/mysqld[0x7e841c]
/lib64/libpthread.so.0[0x3d8640677d]
/lib64/libc.so.6(clone+0x6d)[0x3d85cd3c1d]
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 18:30:14 mysqld_safe mysqld from pid file /var/lib/mysql/hostname.pid ended

I tried to find the reason for this by enabling higher logging, but every time the error log was the same, until I discovered that the innodb_log_file_size was not big enough. I set it to 256MB and it solved the problem:

innodb_log_file_size=256M