// after this ... server went completely dead

Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 [Warning] You need to use --log-bin to make --binlog-format work.
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 InnoDB: The InnoDB memory heap is disabled
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 InnoDB: Compressed tables use zlib 1.2.7
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 InnoDB: Using Linux native AIO
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 InnoDB: Initializing buffer pool, size = 4.0G
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 InnoDB: Completed initialization of buffer pool
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43 InnoDB: highest supported file format is Barracuda.
Mar 24 23:19:43 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:43  InnoDB: Waiting for the background threads to start
Mar 24 23:19:44 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:44 Percona XtraDB (http://www.percona.com) 5.5.34-MariaDB-31.1 started; log sequence number 12506055416
Mar 24 23:19:44 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:44 [Note] Plugin 'FEEDBACK' is disabled.
Mar 24 23:19:45 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:45 [Note] Server socket created on IP: '0.0.0.0'.
Mar 24 23:19:45 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:45 [Note] Event Scheduler: Loaded 0 events
Mar 24 23:19:45 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:45 [Note] /usr/sbin/mysqld: ready for connections.
Mar 24 23:19:45 Debian-70-wheezy-64-minimal mysqld: Version: '5.5.34-MariaDB-1~wheezy-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
Mar 24 23:19:46 Debian-70-wheezy-64-minimal /etc/mysql/debian-start[5687]: Upgrading MySQL tables if necessary.
Mar 24 23:19:46 Debian-70-wheezy-64-minimal /etc/mysql/debian-start[5691]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Mar 24 23:19:46 Debian-70-wheezy-64-minimal /etc/mysql/debian-start[5691]: Looking for 'mysql' as: /usr/bin/mysql
Mar 24 23:19:46 Debian-70-wheezy-64-minimal /etc/mysql/debian-start[5691]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Mar 24 23:19:46 Debian-70-wheezy-64-minimal /etc/mysql/debian-start[5691]: This installation of MySQL is already upgraded to 5.5.34-MariaDB, use --force if you still need to run mysql_upgrade
Mar 24 23:19:46 Debian-70-wheezy-64-minimal /etc/mysql/debian-start[5706]: Checking for insecure root accounts.
Mar 24 23:19:46 Debian-70-wheezy-64-minimal /etc/mysql/debian-start[5711]: Triggering myisam-recover for all MyISAM tables
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: 140324 23:19:51 [ERROR] mysqld got signal 11 ;
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: This could be because you hit a bug. It is also possible that this binary
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: We will try our best to scrape up some info that will hopefully help
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: diagnose the problem, but since we have already crashed, 
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: something is definitely wrong and this may fail.
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: Server version: 5.5.34-MariaDB-1~wheezy-log
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: key_buffer_size=3145728000
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: read_buffer_size=131072
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: max_used_connections=1
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: max_threads=153
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: thread_count=1
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: It is possible that mysqld could use up to 
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3407642 K  bytes of memory
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: Hope that's ok; if not, decrease some variables in the equation.
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: Thread pointer: 0x0x7f4c6c6d6000
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: Attempting backtrace. You can use the following information to find out
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: where mysqld died. If you see no messages after this, something went
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: terribly wrong...
Mar 24 23:19:51 Debian-70-wheezy-64-minimal mysqld: stack_bottom = 0x7f4bd07a8e10 thread_stack 0x30000