service mysql restart; Node crashing after joining to cluster

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

Bug Description

Error in my_thread_global_end(): 2 threads didn't exit
mysqld: /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-new/label_exp/debian-jessie-64bit/percona-xtradb-cluster-5.6-5.6.30-25.16/mysys/my_thr_init.c:207: m y_thread_global_end: Assertion `0' failed.
13:06:43 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=46212576
read_buffer_size=131072
max_used_connections=0
max_threads=302
thread_count=1
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 165436 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x90aaec]
/usr/sbin/mysqld(handle_fatal_signal+0x469)[0x68ac69]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f126454f8d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f1262465067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f1262466448]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e266)[0x7f126245e266]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e312)[0x7f126245e312]
/usr/sbin/mysqld[0x908999]
/usr/sbin/mysqld(my_end+0x70)[0x906030]
/usr/sbin/mysqld[0x5a7ead]
/usr/sbin/mysqld(unireg_abort+0x16f)[0x5af14f]
/usr/sbin/mysqld(_Z18wsrep_sst_receivedP5wsrepRK10wsrep_uuidlPKvm+0x23d)[0x5c3e7d]
/usr/sbin/mysqld(_Z18wsrep_sst_continuev+0xaa)[0x5c3f3a]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x146f)[0x5b642f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f1262451b45]
/usr/sbin/mysqld[0x5a60bd]
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.
160804 15:06:43 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended

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

Can you share complete error log.

It seems like for some reason SST fails but galera doesn't ensure a clean shutdown.
(clean shutdown is existing issue and has been observed as part of other use-cases too
 but may be what is interesting to findout is why SST failed ?)

Revision history for this message
Mike (h-biuro) wrote :
Download full text (30.8 KiB)

Hi! Thanks for reply,

another bug discovered:
server booted, mysql started, synced full transfer.

service mysql stop

netstat -ptan

root@db03:~# netstat -ptan
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:19381 0.0.0.0:* LISTEN 2757/rpc.statd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2828/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20105/master
tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN 2881/nrpe
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2746/rpcbind
tcp 0 0 0.0.0.0:9200 0.0.0.0:* LISTEN 2898/xinetd

------------

root@db03:~# head -400 /var/log/mysqld.log
2016-08-08 11:59:52 4009 [Note] /usr/sbin/mysqld: Normal shutdown

2016-08-08 11:59:52 4009 [Note] WSREP: Stop replication
2016-08-08 11:59:52 4009 [Note] WSREP: Closing send monitor...
2016-08-08 11:59:52 4009 [Note] WSREP: Closed send monitor.
2016-08-08 11:59:52 4009 [Note] WSREP: gcomm: terminating thread
2016-08-08 11:59:52 4009 [Note] WSREP: gcomm: joining thread
2016-08-08 11:59:52 4009 [Note] WSREP: gcomm: closing backend
2016-08-08 11:59:52 4009 [Note] WSREP: view(view_id(NON_PRIM,0ca49fa1,27) memb {
        c8f2477c,0
} joined {
} left {
} partitioned {
        0ca49fa1,0
        c5a86da4,0
})
2016-08-08 11:59:52 4009 [Note] WSREP: New COMPONENT: primary = no, bootstrap = no, my_idx = 0, memb_num = 1
2016-08-08 11:59:52 4009 [Note] WSREP: view((empty))
2016-08-08 11:59:52 4009 [Note] WSREP: gcomm: closed
2016-08-08 11:59:52 4009 [Note] WSREP: Flow-control interval: [16, 16]
2016-08-08 11:59:52 4009 [Note] WSREP: Received NON-PRIMARY.
2016-08-08 11:59:52 4009 [Note] WSREP: Shifting SYNCED -> OPEN (TO: 256135853)
2016-08-08 11:59:52 4009 [Note] WSREP: Received self-leave message.
2016-08-08 11:59:52 4009 [Note] WSREP: New cluster view: global state: cad69e4f-c04d-11e5-ab50-efd4e2ebbb7c:256135853, view# -1: non-Primary, number of nodes: 1, my index: 0, protocol version 3
2016-08-08 11:59:52 4009 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2016-08-08 11:59:52 4009 [Note] WSREP: Flow-control interval: [0, 0]
2016-08-08 11:59:52 4009 [Note] WSREP: Received SELF-LEAVE. Closing connection.
2016-08-08 11:59:52 4009 [Note] WSREP: Shifting OPEN -> CLOSED (TO: 256135853)
2016-08-08 11:59:52 4009 [Note] WSREP: RECV thread exiting 0: Success
2016-08-08 11:59:52 4009 [Note] WSREP: New cluster view: global state: cad69e4f-c04d-11e5-ab50-efd4e2ebbb7c:256135853, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version 3
2016-08-08 11:59:52 4009 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2016-08-08 11:59:52 4009 [Note] WSREP: recv_thread() joined.
2016-08-08 11:59:52 4009 [Note] WSREP: applier thread exiting (code:0)
2016-08-08 11:59:52 4009 [Note] WSREP: Closing replication queue.
2016-08-08 11:59:52 4009 [Note] WSREP: Closing slave action queue.
2016-08-08 11:59:52 4009 ...

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-1917

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.