FSM no such a transition ROLLED_BACK, mysqld got signal 6
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.6 |
Fix Released
|
Critical
|
Krunal Bauskar |
Bug Description
CentOS release 6.5 (Final)
kernel 2.6.32-
Percona-
Percona-
percona-
Percona-
Percona-
percona-
percona-
Percona-
2013-12-16 16:10:06 14575 [Note] WSREP: 0.0 (ISP01-
2013-12-16 16:10:06 14575 [Note] WSREP: Member 0 (ISP01-
2013-12-17 10:30:11 14575 [Warning] WSREP: SQL statement was ineffective, THD: 56, buf: 272
QUERY: UPDATE sys_session SET last_updated = '2013-12-17 10:30:11' WHERE session_id = '3u0g48olu25cev
=> Skipping replication
2013-12-17 10:30:11 14575 [Warning] WSREP: SQL statement was ineffective, THD: 54, buf: 272
QUERY: UPDATE sys_session SET last_updated = '2013-12-17 10:30:11' WHERE session_id = '3u0g48olu25cev
=> Skipping replication
2013-12-17 10:30:11 14575 [ERROR] WSREP: FSM: no such a transition ROLLED_BACK -> ROLLED_BACK
09:30:11 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:/
key_buffer_
read_buffer_
max_used_
max_threads=252
thread_count=25
connection_count=25
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x3f90be0
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 = 7f161520dd38 thread_stack 0x80000
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f15bc100c00): is an invalid pointer
Connection ID (thread ID): 54
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
131217 10:30:11 mysqld_safe Number of processes running now: 0
131217 10:30:11 mysqld_safe WSREP: not restarting wsrep node automatically
131217 10:30:11 mysqld_safe mysqld from pid file /var/run/
Changed in percona-xtradb-cluster: | |
status: | New → Incomplete |
tags: | added: i59934 |
Changed in percona-xtradb-cluster: | |
status: | Expired → New |
Changed in percona-xtradb-cluster: | |
assignee: | nobody → Krunal Bauskar (krunal-bauskar) |
According to variables, you have binlog_ format= STATEMENT, which is not supported atm
Better set to value ROW