140723 22:49:31 mysqld_safe mysqld from pid file /var/lib/mysql/claire.pid ended 140723 22:49:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 140723 22:49:32 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.E10DkC' --pid-file='/var/lib/mysql/claire-recover.pid' /usr/sbin/mysqld: Query cache is disabled (resize or similar command in progress); repeat this command later 140723 22:49:33 mysqld_safe WSREP: Failed to recover position: '140723 22:49:32 [Note] InnoDB: Using mutexes to ref count buffer pool pages 140723 22:49:32 [Note] InnoDB: The InnoDB memory heap is disabled 140723 22:49:32 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 140723 22:49:32 [Note] InnoDB: Compressed tables use zlib 1.2.3 140723 22:49:32 [Note] InnoDB: Using Linux native AIO 140723 22:49:32 [Note] InnoDB: Using CPU crc32 instructions 140723 22:49:32 [Note] InnoDB: Initializing buffer pool, size = 100.0M 140723 22:49:32 [Note] InnoDB: Completed initialization of buffer pool 140723 22:49:32 [Note] InnoDB: Highest supported file format is Barracuda. 140723 22:49:32 [Note] InnoDB: 128 rollback segment(s) are active. 140723 22:49:32 [Note] InnoDB: Waiting for purge to start 140723 22:49:32 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.17-65.0 started; log sequence number 285553557 140723 22:49:32 [Note] Plugin 'FEEDBACK' is disabled. 140723 22:49:32 [ERROR] 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. To report this bug, see http://kb.askmonty.org/en/reporting-bugs 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. Server version: 10.0.12-MariaDB-wsrep key_buffer_size=524288000 read_buffer_size=131072 max_used_connections=0 max_threads=102 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 553304 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7f3bdf394008 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 = 0x7ffff20b5980 thread_stack 0x48000 /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb914fb] /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x743318] /lib64/libpthread.so.0(+0xf710)[0x7f3c0ac06710] /usr/sbin/mysqld[0x6e3149] /usr/sbin/mysqld(_Z12wsrep_commitP10handlertonP3THDb+0x18)[0x6e31b8] /usr/sbin/mysqld[0x7449e6] /usr/sbin/mysqld(_Z15ha_commit_transP3THDb+0x256)[0x746466] /usr/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x29)[0x6b1239] /usr/sbin/mysqld(_Z18close_mysql_tablesP3THD+0x1b)[0x59d5fb] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x11c1)[0x5ebfd1] /usr/sbin/mysqld[0x553c86] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x205d)[0x55652d] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f3c09251d1d] /usr/sbin/mysqld[0x549cb9] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): is an invalid pointer Connection ID (thread ID): 0 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on 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.'