140925 13:23:20 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140925 13:23:20 [Note] Plugin 'FEDERATED' is disabled.
140925 13:23:20 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880
140925 13:23:20 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
140925 13:23:20 InnoDB: The InnoDB memory heap is disabled
140925 13:23:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140925 13:23:20 InnoDB: Compressed tables use zlib 1.2.3.4
140925 13:23:20 InnoDB: Initializing buffer pool, size = 5.0M
140925 13:23:20 InnoDB: Completed initialization of buffer pool
140925 13:23:20 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140925 13:23:20  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...
140925 13:23:20  InnoDB: Waiting for the background threads to start
140925 13:23:21 InnoDB: Error: tablespace size stored in header is 3200 pages, but
140925 13:23:21 InnoDB: the sum of data file sizes is only 2816 pages
140925 13:23:21 InnoDB: 5.5.38 started; log sequence number 1339493768
140925 13:23:21 InnoDB: !!! innodb_force_recovery is set to 1 !!!
140925 13:23:21 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140925 13:23:21 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
140925 13:23:21 [Note] Server socket created on IP: '0.0.0.0'.
InnoDB: Error: trying to access page number 39 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
140925 13:23:21  InnoDB: Assertion failure in thread 2872412992 in file fil0fil.c line 4578
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.
11:23:21 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=16777216
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 = 346075 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+0x33)[0xb727fd93]
/usr/sbin/mysqld(handle_fatal_signal+0x484)[0xb712c134]
[0xb6ddf500]
/usr/sbin/mysqld(+0x594e52)[0xb7396e52]
/usr/sbin/mysqld(+0x595942)[0xb7397942]
/usr/sbin/mysqld(+0x585357)[0xb7387357]
/usr/sbin/mysqld(+0x56faef)[0xb7371aef]
/usr/sbin/mysqld(+0x5294ca)[0xb732b4ca]
/usr/sbin/mysqld(+0x61aea3)[0xb741cea3]
/usr/sbin/mysqld(+0x61b488)[0xb741d488]
/usr/sbin/mysqld(+0x56febf)[0xb7371ebf]
/usr/sbin/mysqld(+0x52976d)[0xb732b76d]
/usr/sbin/mysqld(+0x61b5ee)[0xb741d5ee]
/usr/sbin/mysqld(+0x61bbb4)[0xb741dbb4]
/usr/sbin/mysqld(+0x61c4e7)[0xb741e4e7]
/usr/sbin/mysqld(+0x611c6e)[0xb7413c6e]
/usr/sbin/mysqld(+0x549b61)[0xb734bb61]
/usr/sbin/mysqld(+0x5393be)[0xb733b3be]
/usr/sbin/mysqld(+0x53dcb1)[0xb733fcb1]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb6d5ed4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb6b6d9de]
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.