2015-12-20 21:19:38 12274 [Warning] IP address '45.34.219.6' could not be resolved: Temporary failure in name resolution
2015-12-20 21:19:39 12274 [Warning] IP address '45.34.219.6' could not be resolved: Temporary failure in name resolution
2015-12-20 21:19:40 12274 [Warning] IP address '45.34.219.6' could not be resolved: Temporary failure in name resolution
2015-12-20 21:19:40 12274 [Warning] IP address '45.34.219.6' could not be resolved: Temporary failure in name resolution
2015-12-20 21:19:41 12274 [Warning] IP address '45.34.219.6' could not be resolved: Temporary failure in name resolution
01:00:01 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 XtraDB Cluster better by reporting any
bugs at  https://bugs.launchpad.net/percona-xtradb-cluster 

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=51
max_threads=501
thread_count=50
connection_count=25
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1170062 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2a76c820
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...
Segmentation fault
151221 01:00:01 mysqld_safe Number of processes running now: 0
151221 01:00:01 mysqld_safe WSREP: not restarting wsrep node automatically
151221 01:00:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151221 03:38:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql