Dec  1 23:40:32 database mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] Using unique option prefix 'bind' is error-prone and can break in the future. Please use the full name 'bind-address' instead.
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] /usr/sbin/mysqld (mysqld 10.1.9-MariaDB-1~trusty) starting as process 7121 ...
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: The InnoDB memory heap is disabled
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Memory barrier is not used
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Compressed tables use zlib 1.2.8
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Using Linux native AIO
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Using CPU crc32 instructions
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Completed initialization of buffer pool
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Highest supported file format is Barracuda.
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: 128 rollback segment(s) are active.
Dec  1 23:40:32 database mysqld: 2015-12-02  0:40:32 140261563865024 [Note] InnoDB: Waiting for purge to start
Dec  1 23:40:32 database mysqld: 151202  0:40:32 [ERROR] mysqld got signal 11 ;
Dec  1 23:40:32 database mysqld: This could be because you hit a bug. It is also possible that this binary
Dec  1 23:40:32 database mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Dec  1 23:40:32 database mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Dec  1 23:40:32 database mysqld:
Dec  1 23:40:32 database mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
Dec  1 23:40:32 database mysqld:
Dec  1 23:40:32 database mysqld: We will try our best to scrape up some info that will hopefully help
Dec  1 23:40:32 database mysqld: diagnose the problem, but since we have already crashed,
Dec  1 23:40:32 database mysqld: something is definitely wrong and this may fail.
Dec  1 23:40:32 database mysqld:
Dec  1 23:40:32 database mysqld: Server version: 10.1.9-MariaDB-1~trusty
Dec  1 23:40:32 database mysqld: key_buffer_size=16777216
Dec  1 23:40:32 database mysqld: read_buffer_size=131072
Dec  1 23:40:32 database mysqld: max_used_connections=0
Dec  1 23:40:32 database mysqld: max_threads=153
Dec  1 23:40:32 database mysqld: thread_count=0
Dec  1 23:40:32 database mysqld: It is possible that mysqld could use up to
Dec  1 23:40:32 database mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352416 K  bytes of memory
Dec  1 23:40:32 database mysqld: Hope that's ok; if not, decrease some variables in the equation.
Dec  1 23:40:32 database mysqld:
Dec  1 23:40:32 database mysqld: Thread pointer: 0x0x0
Dec  1 23:40:32 database mysqld: Attempting backtrace. You can use the following information to find out
Dec  1 23:40:32 database mysqld: where mysqld died. If you see no messages after this, something went
Dec  1 23:40:32 database mysqld: terribly wrong...
Dec  1 23:40:32 database mysqld: stack_bottom = 0x0 thread_stack 0x30000
Dec  1 23:40:32 database mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f913044f5ae]
Dec  1 23:40:32 database mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x7f912ff7f47d]
Dec  1 23:40:32 database mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f912e4dd340]
Dec  1 23:40:32 database mysqld: /usr/sbin/mysqld(+0x8df809)[0x7f91302b5809]
Dec  1 23:40:32 database mysqld: /usr/sbin/mysqld(+0x8ae12d)[0x7f913028412d]
Dec  1 23:40:32 database mysqld: /usr/sbin/mysqld(+0x875487)[0x7f913024b487]
Dec  1 23:40:32 database mysqld: /usr/sbin/mysqld(+0x8dc2fe)[0x7f91302b22fe]
Dec  1 23:40:32 database mysqld: /usr/sbin/mysqld(+0x8ca1f0)[0x7f91302a01f0]
Dec  1 23:40:32 database mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f912e4d5182]
Dec  1 23:40:32 database mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f912dbf847d]
Dec  1 23:40:32 database mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Dec  1 23:40:32 database mysqld: information that should help you find out what is causing the crash.
Dec  1 23:40:32 database mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Dec  1 23:41:02 database /etc/init.d/mysql[7423]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Dec  1 23:41:02 database /etc/init.d/mysql[7423]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Dec  1 23:41:02 database /etc/init.d/mysql[7423]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")'
Dec  1 23:41:02 database /etc/init.d/mysql[7423]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Dec  1 23:41:02 database /etc/init.d/mysql[7423]: