| 2016-12-02 11:16:35 |
Nobuto Murata |
description |
percona-cluter charm deployment, it stopped with an error and mysql daemon did not accept any read/write. So I found mysqld crashed during the cluster deployment.
[/var/log/mysql/error.log]
WSREP_SST: [INFO] Evaluating innobackupex --defaults-file=/etc/mysql/my.cnf --no-version-check $tmpopts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2>${DATA}/innobackup.backup.log | socat -u stdio TCP:10.0.0.96:4444; RC=( ${PIPESTATUS[@]} ) (20161202 10:30:51.554)
10:30:56 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=33554432
read_buffer_size=131072
max_used_connections=78
max_threads=20002
thread_count=39
connection_count=37
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8017301 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x53a8f40
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 = 7fc4a5797e58 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x9176db]
/usr/sbin/mysqld(handle_fatal_signal+0x378)[0x663418]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113e0)[0x7fc65a1de3e0]
[0x7fc3f80000d8]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 192
Status: KILL_CONNECTION
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.
WSREP_SST: [ERROR] innobackupex finished with error: 9. Check /var/lib/percona-xtradb-cluster//innobackup.backup.log (20161202 10:30:56.012) |
ii percona-galera-3 3.8-3390-0ubuntu6 amd64 Galera replication framework for Percona XtraDB Cluster
ii percona-xtrabackup 2.2.3-2.1build1.1 amd64 Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-server-5.6 5.6.21-25.8-0ubuntu3.2 amd64 Percona XtraDB Cluster database server binaries
percona-cluter charm deployment stopped with an error and mysql daemon did not accept any read/write. So I found mysqld crashed during the cluster deployment.
[/var/log/mysql/error.log]
WSREP_SST: [INFO] Evaluating innobackupex --defaults-file=/etc/mysql/my.cnf --no-version-check $tmpopts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2>${DATA}/innobackup.backup.log | socat -u stdio TCP:10.0.0.96:4444; RC=( ${PIPESTATUS[@]} ) (20161202 10:30:51.554)
10:30:56 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=33554432
read_buffer_size=131072
max_used_connections=78
max_threads=20002
thread_count=39
connection_count=37
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8017301 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x53a8f40
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 = 7fc4a5797e58 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x9176db]
/usr/sbin/mysqld(handle_fatal_signal+0x378)[0x663418]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113e0)[0x7fc65a1de3e0]
[0x7fc3f80000d8]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 192
Status: KILL_CONNECTION
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.
WSREP_SST: [ERROR] innobackupex finished with error: 9. Check /var/lib/percona-xtradb-cluster//innobackup.backup.log (20161202 10:30:56.012) |
|
