Constant Galera Crashes

Bug #1483333 reported by Jason Mallory
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Expired
Undecided
Unassigned

Bug Description

09:36:59 UTC - mysqld got signal 6 ;
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=25165824
read_buffer_size=131072
max_used_connections=13
max_threads=152
thread_count=19
connection_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3781883 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x113974c0
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 = 7fa794237d38 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8fa965]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x665644]
/lib64/libpthread.so.0[0x305b60f710]
/lib64/libc.so.6(gsignal+0x35)[0x305b232625]
/lib64/libc.so.6(abort+0x175)[0x305b233e05]
/usr/lib64/libgalera_smm.so(_ZN6galera3FSMINS_9TrxHandle5StateENS1_10TransitionENS_10EmptyGuardENS_11EmptyActionEE8shift_toES2_+0x188)[0x7fab9fcd7d68]
/usr/lib64/libgalera_smm.so(_ZN6galera13ReplicatorSMM13post_rollbackEPNS_9TrxHandleE+0x2e)[0x7fab9fcf29de]
/usr/lib64/libgalera_smm.so(galera_post_rollback+0x68)[0x7fab9fd0c1e8]
/usr/sbin/mysqld[0x7a906e]
/usr/sbin/mysqld(_Z15ha_rollback_lowP3THDb+0x97)[0x5a5057]
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG8rollbackEP3THDb+0x10f)[0x8b26ff]
/usr/sbin/mysqld(_Z17ha_rollback_transP3THDb+0x74)[0x5a4e24]
/usr/sbin/mysqld(_Z15ha_commit_transP3THDbb+0x312)[0x5a5702]
/usr/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x35)[0x78e495]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x954)[0x6ea7b4]
/usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x60)[0x82ed50]
/usr/sbin/mysqld(_ZN12sp_lex_instr23reset_lex_and_exec_coreEP3THDPjb+0x228)[0x82f088]
/usr/sbin/mysqld(_ZN12sp_lex_instr29validate_lex_and_execute_coreEP3THDPjb+0x8f)[0x830a6f]
/usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x2b0)[0x831b20]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x782)[0x66c442]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x707)[0x66d997]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x19cf)[0x6eb82f]
/usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x60)[0x82ed50]
/usr/sbin/mysqld(_ZN12sp_lex_instr23reset_lex_and_exec_coreEP3THDPjb+0x228)[0x82f088]
/usr/sbin/mysqld(_ZN12sp_lex_instr29validate_lex_and_execute_coreEP3THDPjb+0x8f)[0x830a6f]
/usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x2b0)[0x831b20]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x782)[0x66c442]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x707)[0x66d997]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x19cf)[0x6eb82f]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x658)[0x6f0958]
/usr/sbin/mysqld[0x6f0acd]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x19d5)[0x6f2de5]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x22b)[0x6f42cb]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x6bc52f]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6bc717]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xaf611a]
/lib64/libpthread.so.0[0x305b6079d1]
/lib64/libc.so.6(clone+0x6d)[0x305b2e88fd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa487440b90): is an invalid pointer
Connection ID (thread ID): 25603
Status: NOT_KILLED

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.

Revision history for this message
Krunal Bauskar (krunal-bauskar) wrote :

Can you attached the log file.

I suspect the last command before the crash has skipped replication
and if that is the case and interpreting the stack trace I assume you are hitting
https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1292842

(We have recently fixed it and will be included in next release)

Changed in percona-xtradb-cluster:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona XtraDB Cluster because there has been no activity for 60 days.]

Changed in percona-xtradb-cluster:
status: Incomplete → Expired
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1842

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.