Comment 3 for bug 1629566

Revision history for this message
Przemek (pmalkowski) wrote :

This happens also on Galera cluster binaries from Codership:

[root@83878f054a4c /]# rpm -qa|grep -i mysql
perl-DBD-MySQL-4.013-3.el6.x86_64
mysql-wsrep-client-5.6-5.6.33-25.17.el6.x86_64
mysql-wsrep-5.6-5.6.33-25.17.el6.x86_64
mysql-wsrep-libs-compat-5.6-5.6.33-25.17.el6.x86_64
mysql-wsrep-server-5.6-5.6.33-25.17.el6.x86_64

mysql> select @@version,@@version_comment;
+-----------+-------------------------------------------+
| @@version | @@version_comment |
+-----------+-------------------------------------------+
| 5.6.33 | MySQL Community Server (GPL), wsrep_25.17 |
+-----------+-------------------------------------------+
1 row in set (0.00 sec)

mysql> set global wsrep_desync=0;
Query OK, 0 rows affected (0.01 sec)

mysql> show status like 'ws%';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR:
Can't connect to the server

2016-10-10 07:05:04 868 [Note] WSREP: Member 1.0 (galera1) requested state transfer from '*any*'. Selected 0.0 (83878f054a4c)(SYNCED) as donor.
2016-10-10 07:05:04 868 [Note] WSREP: Shifting SYNCED -> DONOR/DESYNCED (TO: 68)
2016-10-10 07:05:04 868 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2016-10-10 07:05:04 868 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'donor' --address '172.17.0.4:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/my.cnf' --defaults-group-suffix '' '' --gtid 'c8d6c713-89c1-11e6-af94-2b7d3c8cd95f:68''
2016-10-10 07:05:04 868 [Note] WSREP: sst_donor_thread signaled with 0
WSREP_SST: [INFO] Streaming with xbstream (20161010 07:05:04.234)
WSREP_SST: [INFO] Using socat as streamer (20161010 07:05:04.236)
WSREP_SST: [INFO] Using /tmp/tmp.XpXn6B67ok as xtrabackup temporary directory (20161010 07:05:04.250)
WSREP_SST: [INFO] Using /tmp/tmp.yY5HBbDHLi as innobackupex temporary directory (20161010 07:05:04.253)
WSREP_SST: [INFO] Streaming GTID file before SST (20161010 07:05:04.257)
WSREP_SST: [INFO] Evaluating xbstream -c ${INFO_FILE} | socat -u stdio TCP:172.17.0.4:4444; RC=( ${PIPESTATUS[@]} ) (20161010 07:05:04.258)
WSREP_SST: [INFO] Sleeping before data transfer for SST (20161010 07:05:04.263)
WSREP_SST: [INFO] Streaming the backup to joiner at 172.17.0.4 4444 (20161010 07:05:14.266)
WSREP_SST: [INFO] Evaluating innobackupex --defaults-file=/etc/my.cnf --defaults-group=mysqld --no-version-check $tmpopts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2>${DATA}/innobackup.backup.log | socat -u stdio TCP:172.17.0.4:4444; RC=( ${PIPESTATUS[@]} ) (20161010 07:05:14.267)
2016-10-10 07:05:18 868 [Note] WSREP: Provider paused at c8d6c713-89c1-11e6-af94-2b7d3c8cd95f:68 (95)
2016-10-10 07:05:19 868 [Note] WSREP: resuming provider at 95
2016-10-10 07:05:19 868 [Note] WSREP: Provider resumed.
2016-10-10 07:05:19 868 [Note] WSREP: 0.0 (83878f054a4c): State transfer to 1.0 (galera1) complete.
2016-10-10 07:05:19 868 [Note] WSREP: Shifting DONOR/DESYNCED -> JOINED (TO: 68)
2016-10-10 07:05:19 868 [Warning] WSREP: SYNC message sender from non-JOINED 0.0 (83878f054a4c). Ignored.
WSREP_SST: [INFO] Total time on donor: 0 seconds (20161010 07:05:19.264)
WSREP_SST: [INFO] Cleaning up temporary directories (20161010 07:05:19.266)
2016-10-10 07:05:29 868 [Note] WSREP: 1.0 (galera1): State transfer from 0.0 (83878f054a4c) complete.
2016-10-10 07:05:29 868 [Note] WSREP: Member 1.0 (galera1) synced with group.
2016-10-10 07:06:42 868 [Note] WSREP: 0.0 (83878f054a4c): State transfer to 1.0 (galera1) complete.
2016-10-10 07:06:42 868 [ERROR] WSREP: FSM: no such a transition JOINED -> JOINED
07:06:42 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.

key_buffer_size=25165824
read_buffer_size=131072
max_used_connections=11
max_threads=200
thread_count=6
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 104043 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f2940000990
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 = 7f29881c6988 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x90f145]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x686624]
/lib64/libpthread.so.0(+0xf7e0)[0x7f29972417e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f299589b5e5]
/lib64/libc.so.6(abort+0x175)[0x7f299589cdc5]
/usr/lib64/galera-3/libgalera_smm.so(_ZN6galera3FSMINS_10Replicator5StateENS_13ReplicatorSMM10TransitionENS_10EmptyGuardENS_11EmptyActionEE8shift_toES2_+0x188)[0x7f2993e2ae18]
/usr/lib64/galera-3/libgalera_smm.so(_ZN6galera13ReplicatorSMM12process_joinEll+0x175)[0x7f2993e23db5]
/usr/lib64/galera-3/libgalera_smm.so(_ZN6galera15GcsActionSource8dispatchEPvRK10gcs_actionRb+0x235)[0x7f2993e003f5]
/usr/lib64/galera-3/libgalera_smm.so(_ZN6galera15GcsActionSource7processEPvRb+0x63)[0x7f2993e00aa3]
/usr/lib64/galera-3/libgalera_smm.so(_ZN6galera13ReplicatorSMM10async_recvEPv+0x93)[0x7f2993e26933]
/usr/lib64/galera-3/libgalera_smm.so(galera_recv+0x23)[0x7f2993e35543]
/usr/sbin/mysqld[0x5c0051]
/usr/sbin/mysqld(start_wsrep_THD+0x46b)[0x5ae51b]
/lib64/libpthread.so.0(+0x7aa1)[0x7f2997239aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f2995951aad]

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): 5
Status: NOT_KILLED