May 26 13:12:17 raspberrypi mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a f$
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be rem$
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 [Note] Plugin 'FEDERATED' is disabled.
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 InnoDB: The InnoDB memory heap is disabled
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 InnoDB: Compressed tables use zlib 1.2.7
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 InnoDB: Using Linux native AIO
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 InnoDB: Initializing buffer pool, size = 128.0M
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 InnoDB: Completed initialization of buffer pool
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17 InnoDB: highest supported file format is Barracuda.
May 26 13:12:17 raspberrypi mysqld: InnoDB: The log sequence number in ibdata files does not match
May 26 13:12:17 raspberrypi mysqld: InnoDB: the log sequence number in the ib_logfiles!
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17  InnoDB: Database was not shut down normally!
May 26 13:12:17 raspberrypi mysqld: InnoDB: Starting crash recovery.
May 26 13:12:17 raspberrypi mysqld: InnoDB: Reading tablespace information from the .ibd files...
May 26 13:12:17 raspberrypi mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
May 26 13:12:17 raspberrypi mysqld: InnoDB: buffer...
May 26 13:12:17 raspberrypi mysqld: InnoDB: Error: trying to access page number 4294896512 in space 0,
May 26 13:12:17 raspberrypi mysqld: InnoDB: space name ./ibdata1,
May 26 13:12:17 raspberrypi mysqld: InnoDB: which is outside the tablespace bounds.
May 26 13:12:17 raspberrypi mysqld: InnoDB: Byte offset 0, len 16384, i/o type 10.
May 26 13:12:17 raspberrypi mysqld: InnoDB: If you get this error at mysqld startup, please check that
May 26 13:12:17 raspberrypi mysqld: InnoDB: Byte offset 0, len 16384, i/o type 10.
May 26 13:12:17 raspberrypi mysqld: InnoDB: If you get this error at mysqld startup, please check that
May 26 13:12:17 raspberrypi mysqld: InnoDB: your my.cnf matches the ibdata files that you have in the
May 26 13:12:17 raspberrypi mysqld: InnoDB: MySQL server.
May 26 13:12:17 raspberrypi mysqld: 150526 13:12:17  InnoDB: Assertion failure in thread 1987236768 in file fil0fil.c line 4578
May 26 13:12:17 raspberrypi mysqld: InnoDB: We intentionally generate a memory trap.
May 26 13:12:17 raspberrypi mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 26 13:12:17 raspberrypi mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 26 13:12:17 raspberrypi mysqld: InnoDB: immediately after the mysqld startup, there may be
May 26 13:12:17 raspberrypi mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 26 13:12:17 raspberrypi mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
May 26 13:12:17 raspberrypi mysqld: InnoDB: about forcing recovery.
May 26 13:12:17 raspberrypi mysqld: 11:12:17 UTC - mysqld got signal 6 ;
May 26 13:12:17 raspberrypi mysqld: This could be because you hit a bug. It is also possible that this binary
May 26 13:12:17 raspberrypi mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 26 13:12:17 raspberrypi mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 26 13:12:17 raspberrypi mysqld: We will try our best to scrape up some info that will hopefully help
May 26 13:12:17 raspberrypi mysqld: diagnose the problem, but since we have already crashed,
May 26 13:12:17 raspberrypi mysqld: something is definitely wrong and this may fail.
May 26 13:12:17 raspberrypi mysqld:
May 26 13:12:17 raspberrypi mysqld: key_buffer_size=16777216
May 26 13:12:17 raspberrypi mysqld: read_buffer_size=131072
May 26 13:12:17 raspberrypi mysqld: max_used_connections=0
May 26 13:12:17 raspberrypi mysqld: max_threads=151
May 26 13:12:17 raspberrypi mysqld: thread_count=0
May 26 13:12:17 raspberrypi mysqld: connection_count=0
May 26 13:12:17 raspberrypi mysqld: It is possible that mysqld could use up to
May 26 13:12:17 raspberrypi mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346093 K  bytes of memory
May 26 13:12:17 raspberrypi mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 26 13:12:17 raspberrypi mysqld:
May 26 13:12:17 raspberrypi mysqld: Thread pointer: 0x0
May 26 13:12:17 raspberrypi mysqld: Attempting backtrace. You can use the following information to find out
May 26 13:12:17 raspberrypi mysqld: where mysqld died. If you see no messages after this, something went
May 26 13:12:17 raspberrypi mysqld: terribly wrong...
May 26 13:12:17 raspberrypi mysqld: stack_bottom = 0 thread_stack 0x30000
May 26 13:12:17 raspberrypi mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 26 13:12:17 raspberrypi mysqld: information that should help you find out what is causing the crash.
May 26 13:12:18 raspberrypi mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
May 26 13:12:31 raspberrypi /etc/init.d/mysql[5568]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
May 26 13:12:31 raspberrypi /etc/init.d/mysql[5568]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
May 26 13:12:31 raspberrypi /etc/init.d/mysql[5568]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
May 26 13:12:31 raspberrypi /etc/init.d/mysql[5568]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
May 26 13:12:31 raspberrypi /etc/init.d/mysql[5568]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
May 26 13:12:31 raspberrypi /etc/init.d/mysql[5568]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
May 26 13:12:31 raspberrypi /etc/init.d/mysql[5568]: