To see the exact error, I executed the following: root@percona-test:~# service mysql stop * Stopping MySQL (Percona XtraDB Cluster) mysqld ...done. root@percona-test:~# rm /var/lib/mysql/tc.log root@percona-test:~# cat tfile USE mysql; UPDATE user SET password=PASSWORD("root") WHERE user='root'; FLUSH PRIVILEGES; root@percona-test:~# mysqld --bootstrap --user=mysql --skip-grant-tables < tfile 160415 3:31:31 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. root@percona-test:~# echo $? 1 [/var/log/mysql/error.log] 160415 3:31:31 [Note] WSREP: Read nil XID from storage engines, skipping position init 160415 3:31:31 [Note] WSREP: wsrep_load(): loading provider library 'none' 160415 3:31:31 [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. 160415 3:31:31 [Note] Plugin 'FEDERATED' is disabled. 160415 3:31:31 InnoDB: The InnoDB memory heap is disabled 160415 3:31:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins 160415 3:31:31 InnoDB: Compressed tables use zlib 1.2.8 160415 3:31:31 InnoDB: Using Linux native AIO 160415 3:31:31 InnoDB: Initializing buffer pool, size = 128.0M 160415 3:31:31 InnoDB: Completed initialization of buffer pool 160415 3:31:31 InnoDB: highest supported file format is Barracuda. 160415 3:31:31 InnoDB: Waiting for the background threads to start 160415 3:31:32 Percona XtraDB (http://www.percona.com) 5.5.37-35.0-35.0 started; log sequence number 1598129 03:31:32 UTC - 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. 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. Please help us make Percona XtraDB Cluster better by reporting any bugs at https://bugs.launchpad.net/percona-xtradb-cluster key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_threads=153 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 = 351266 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 mysqld(my_print_stacktrace+0x44)[0x2924bcf4] mysqld(handle_fatal_signal+0x500)[0x290971c0] [0x3fff9bfc0478] mysqld(_ZN11TC_LOG_MMAP4openEPKc+0x6f4)[0x2917fd54] mysqld(_ZN11TC_LOG_MMAP4openEPKc+0x2cc)[0x2917f92c] mysqld(+0x2a5e1c)[0x28ea5e1c] mysqld(_Z11mysqld_mainiPPc+0x808)[0x28ea8f58] mysqld(main+0x20)[0x28e862d0] /lib/powerpc64le-linux-gnu/libc.so.6(+0x24d00)[0x3fff9b824d00] /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xc8)[0x3fff9b824ef8] You may download the Percona XtraDB Cluster operations manual by visiting http://www.percona.com/software/percona-xtradb-cluster/. You may find information in the manual which will help you identify the cause of the crash.