Percona XtraDB crashed

It seems the “primary” cluster member crashed unexpectedly. The log is as follow:

………….
140122 10:30:19 [Note] WSREP: gcomm: connected
140122 10:30:19 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636
140122 10:30:19 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 0)
140122 10:30:19 [Note] WSREP: Opened channel ‘mysql_cluster’
140122 10:30:19 [Note] WSREP: New COMPONENT: primary = no, bootstrap = no, my_idx = 0, memb_num = 1
140122 10:30:19 [Note] WSREP: Flow-control interval: [16, 16]
140122 10:30:19 [Note] WSREP: Received NON-PRIMARY.
140122 10:30:19 [Note] WSREP: Waiting for SST to complete.
140122 10:30:19 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 3
140122 10:30:19 [Note] WSREP: New cluster view: global state: 9f9985f1-345e-11e3-bb4d-ee083db0a078:142366, view# -1: non-Primary, number of nodes: 1, my index: 0, protocol version -1
140122 10:30:19 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
140122 10:30:19 [Note] WSREP: STATE_EXCHANGE: sent state UUID: 30f38869-8350-11e3-af76-9b6a0c2200b9
140122 10:30:19 [Note] WSREP: STATE EXCHANGE: sent state msg: 30f38869-8350-11e3-af76-9b6a0c2200b9
140122 10:30:19 [Note] WSREP: STATE EXCHANGE: got state msg: 30f38869-8350-11e3-af76-9b6a0c2200b9 from 0 (primary.mysql.com)
140122 10:30:19 [Note] WSREP: STATE EXCHANGE: got state msg: 30f38869-8350-11e3-af76-9b6a0c2200b9 from 1 (tertiary.mysql.com)
140122 10:30:19 [Note] WSREP: STATE EXCHANGE: got state msg: 30f38869-8350-11e3-af76-9b6a0c2200b9 from 2 (secondary.mysql.com)
140122 10:30:19 [Note] WSREP: Quorum results:
version = 2,
component = PRIMARY,
conf_id = 1406,
members = 3/3 (joined/total),
act_id = 142366,
last_appl. = -1,
protocols = 0/4/2 (gcs/repl/appl),
group UUID = 9f9985f1-345e-11e3-bb4d-ee083db0a078
140122 10:30:19 [Note] WSREP: Flow-control interval: [28, 28]
140122 10:30:19 [Note] WSREP: Restored state OPEN -> JOINED (142366)
140122 10:30:19 [Note] WSREP: New cluster view: global state: 9f9985f1-345e-11e3-bb4d-ee083db0a078:142366, view# 1407: Primary, number of nodes: 3, my index: 0, protocol version 2
140122 10:30:19 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
140122 10:30:19 [Note] WSREP: Assign initial position for certification: 142366, protocol version: 2
140122 10:30:19 [Note] WSREP: Member 0 (primary.mysql.com) synced with group.
140122 10:30:19 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 142366)
140122 10:30:19 [Note] WSREP: Synchronized with group, ready for connections
140122 10:30:19 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
10:33:17 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 Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 334862 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f1aa4000990
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 = 7f1abc217db8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7d8405]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x6b0804]
/lib64/libpthread.so.0[0x348940f500]
/usr/sbin/mysqld(_Z11plugin_lockP3THDPP13st_plugin_int+0x9c)[0x5aa31c]
/usr/sbin/mysqld(_Z21ha_default_handlertonP3THD+0x33)[0x6b3c33]
/usr/sbin/mysqld(_Z14open_table_defP3THDP11TABLE_SHAREj+0x18f9)[0x6219e9]
/usr/sbin/mysqld(_Z15get_table_shareP3THDP10TABLE_LISTPcjjPij+0x1b2)[0x5598f2]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x42f)[0x56331f]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x4a5)[0x564885]
/usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x44)[0x565384]
/usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0xada)[0x75a20a]
/usr/sbin/mysqld(_Z14wsrep_apply_cbPvPKvml+0x284)[0x59a4a4]
/usr/lib64/libgalera_smm.so(+0x18d8ad)[0x7f1abe4ec8ad]
/usr/lib64/libgalera_smm.so(_ZN6galera13ReplicatorSMM9apply_trxEPvPNS_9TrxHandleE+0x223)[0x7f1abe4ef3e3]
/usr/lib64/libgalera_smm.so(_ZN6galera13ReplicatorSMM11process_trxEPvPNS_9TrxHandleE+0x45)[0x7f1abe4efcd5]
/usr/lib64/libgalera_smm.so(_ZN6galera15GcsActionSource8dispatchEPvRK10gcs_action+0x2bc)[0x7f1abe4cd86c]
/usr/lib64/libgalera_smm.so(_ZN6galera15GcsActionSource7processEPv+0x58)[0x7f1abe4cdd28]
/usr/lib64/libgalera_smm.so(_ZN6galera13ReplicatorSMM10async_recvEPv+0x7d)[0x7f1abe4eb93d]
/usr/lib64/libgalera_smm.so(galera_recv+0x23)[0x7f1abe5021e3]
/usr/sbin/mysqld(_Z25wsrep_replication_processP3THD+0x40)[0x599840]
/usr/sbin/mysqld(start_wsrep_THD+0x3b8)[0x51fa38]
/lib64/libpthread.so.0[0x3489407851]
/lib64/libc.so.6(clone+0x6d)[0x3488ce894d]

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

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
140122 10:33:17 mysqld_safe mysqld from pid file /var/lib/mysql/primary.mysql.com.pid ended

Regards,

Andrew

Can you give us more info… like Pxc version,OS etc… and also summary of server hardware details…
might be possible that mysql could be running out of resources…! i think its better to post in http://bugs.percona.com/ if this is a bug

Percona Server 5.5.16 the OS is CentOS 6 64bit with 1GB ram.

I’m not sure its a bug though.

1 GB RAM!!, dont you think this is less when compared to standard setup!, is this a server or VM…?
its better u increase RAM to 2GB or more and then try once again.

It would be better if u can post more info about the setup, the percona config, the centos is with Gui or without…? and r u running any other services in that server…?

Well centos without gui and apache is running but nothing else and we use apache only for phpmyadmin.

I’m trying to tweak my.cnf now to see if it work that way.