# How does one troubleshoot a server crashing? **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [July 18, 2014, 10:31am UTC](https://forums.percona.com/t/how-does-one-troubleshoot-a-server-crashing/3625 "2014-07-18T10:31:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![MacKiller](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@MacKiller](https://forums.percona.com/u/MacKiller)\ **Post date:** [July 18, 2014, 10:31am UTC](https://forums.percona.com/t/how-does-one-troubleshoot-a-server-crashing/3625/1 "2014-07-18T10:31:07Z")
Hi folks, New to the Percona scene and I suppose still green at Linux development (coming from Windows and firmware development). How do I help? I have a server in a Percona XtraDB cluster of three that crashes often (1-3x a day) and recovers. How do I find out if this is a bug that I need to submit, or someone already submitted the bug, or if there is a fix already? For instance, I am going to paste my log here, and I know one of you will probably point me the way, but can you also tell me how you found the answer and if I should submit as a bug (and how)? [URL][https://bugs.launchpad.net/percona-xtradb-cluster[/URL]](https://bugs.launchpad.net/percona-xtradb-cluster%5B/URL%5D) is still a bit cryptic to me. Thanks! * * * 2014-07-18 02:53:45 26203 [Note] WSREP: (9f3d8a11-0e46-11e4-8791-83304bc0dc9b, ‘tcp://0.0.0.0:4567’) reconnecting to 426b8225-0db1-11e4-9736-f28d21187f64 (tcp://10.10.10.31:4567), attempt 0 2014-07-18 02:53:48 26203 [Note] WSREP: (9f3d8a11-0e46-11e4-8791-83304bc0dc9b, ‘tcp://0.0.0.0:4567’) address ‘tcp://10.10.10.32:4567’ pointing to uuid 9f3d8a11-0e46-11e4-8791-83304bc0dc9b is blacklisted, skipping 2014-07-18 02:53:49 26203 [Note] WSREP: (9f3d8a11-0e46-11e4-8791-83304bc0dc9b, ‘tcp://0.0.0.0:4567’) reconnecting to c203f600-0db1-11e4-8989-6bba6abcb41f (tcp://10.10.10.33:4567), attempt 0 2014-07-18 02:53:49 26203 [Note] WSREP: (9f3d8a11-0e46-11e4-8791-83304bc0dc9b, ‘tcp://0.0.0.0:4567’) cleaning up duplicate 0x7fa1a401e220 after established 0x7fa1a40058e0 07:53:49 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 [URL][https://bugs.launchpad.net/percona-xtradb-cluster[/URL]](https://bugs.launchpad.net/percona-xtradb-cluster%5B/URL%5D) key\_buffer\_size=25165824 read\_buffer\_size=131072 max\_used\_connections=12 max\_threads=202 thread\_count=10 connection\_count=10 It is possible that mysqld could use up to key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 105157 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+0x2e)[0x8ea56e] /usr/sbin/mysqld(handle\_fatal\_signal+0x4a4)[0x68d2f4] /lib/x86\_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fa2113f8cb0] [0x7fa1a40001da] You may download the Percona XtraDB Cluster operations manual by visiting [URL][http://www.percona.com/software/percona-xtradb-cluster/[/URL]](http://www.percona.com/software/percona-xtradb-cluster/%5B/URL%5D). You may find information in the manual which will help you identify the cause of the crash. 140718 02:53:50 mysqld\_safe Number of processes running now: 0 140718 02:53:50 mysqld\_safe WSREP: not restarting wsrep node automatically 140718 02:53:50 mysqld\_safe mysqld from pid file /var/lib/mysql/mysqld.pid ended 140718 02:55:17 mysqld\_safe Starting mysqld daemon with databases from /var/lib/mysql 140718 02:55:17 mysqld\_safe WSREP: Running position recovery with --log\_error=‘/var/lib/mysql/wsrep\_recovery.vAqfRP’ --pid-file=‘/var/lib/mysql/NODE2-recover.pid’ 140718 02:56:33 mysqld\_safe WSREP: Recovered position b33d11f5-cbed-11e3-a1d5-ea0534d9f1f5:125617 2014-07-18 02:56:36 0 [Note] WSREP: wsrep\_start\_position var submitted: ‘b33d11f5-cbed-11e3-a1d5-ea0534d9f1f5:125617’ 2014-07-18 02:56:36 12539 [Note] WSREP: Read nil XID from storage engines, skipping position init 2014-07-18 02:56:36 12539 [Note] WSREP: wsrep\_load(): loading provider library ‘/usr/lib/libgalera\_smm.so’ 2014-07-18 02:56:36 12539 [Note] WSREP: wsrep\_load(): Galera 3.5(r178) by Codership Oy loaded successfully. 2014-07-18 02:56:36 12539 [Note] WSREP: CRC-32C: using “slicing-by-8” algorithm. 2014-07-18 02:56:36 12539 [Note] WSREP: Found saved state: b33d11f5-cbed-11e3-a1d5-ea0534d9f1f5:-1 2014-07-18 02:56:36 12539 [Note] WSREP: Passing config to GCS: base\_host = 10.10.10.32; base\_port = 4567; cert.log\_conflicts = no; debug = no; evs.inactive\_check\_period = PT10S; evs.inactive\_timeout = PT1M; evs.install\_timeout = PT1M; evs.join\_retrans\_period = PT1S; evs.keepalive\_period = PT3S; evs.max\_install\_timeouts = 1; evs.send\_window = 1024; evs.stats\_report\_period = PT1M; evs.suspect\_timeout = PT30S; evs.user\_send\_window = 512; evs.view\_forget\_timeout = PT24H; gcache.dir = /var/lib/mysql/; gcache.keep\_pages\_size = 0; gcache.mem\_size = 0; gcache.name = /var/lib/mysql//galera.cache; gcache.page\_size = 128M; gcache.size = 1024M; gcs.fc\_debug = 0; gcs.fc\_factor = 1.0; gcs.fc\_limit = 16; gcs.fc\_master\_slave = no; gcs.max\_packet\_size = 64500; gcs.max\_throttle = 0.25; gcs.recv\_q\_hard\_limit = 9223372036854775807; gcs.recv\_q\_soft\_limit = 0.25; gcs.sync\_donor = no; gmcast.segment = 2; gmcast.version = 0; pc.announce\_timeout = PT3S; pc.checksum = false; pc.ignore\_quorum = false; pc.ignore\_sb = false; pc.npvo = false; pc.version = 0; pc.wait\_pri 2014-07-18 02:56:37 12539 [Note] WSREP: Service thread queue flushed. 2014-07-18 02:56:37 12539 [Note] WSREP: Assign initial position for certification: 125617, protocol version: -1 2014-07-18 02:56:37 12539 [Note] WSREP: wsrep\_sst\_grab() 2014-07-18 02:56:37 12539 [Note] WSREP: Start replication 2014-07-18 02:56:37 12539 [Note] WSREP: Setting initial position to b33d11f5-cbed-11e3-a1d5-ea0534d9f1f5:125617 2014-07-18 02:56:37 12539 [Note] WSREP: protonet asio version 0 2014-07-18 02:56:37 12539 [Note] WSREP: Using CRC-32C (optimized) for message checksums. 2014-07-18 02:56:37 12539 [Note] WSREP: backend: asio 2014-07-18 02:56:37 12539 [Note] WSREP: GMCast version 0 2014-07-18 02:56:37 12539 [Note] WSREP: (0b521a5e-0e51-11e4-b422-ee6e10b1721f, ‘tcp://0.0.0.0:4567’) listening at tcp://0.0.0.0:4567 2014-07-18 02:56:37 12539 [Note] WSREP: (0b521a5e-0e51-11e4-b422-ee6e10b1721f, ‘tcp://0.0.0.0:4567’) multicast: , ttl: 1 2014-07-18 02:56:37 12539 [Note] WSREP: EVS version 0 2014-07-18 02:56:37 12539 [Note] WSREP: PC version 0 2014-07-18 02:56:37 12539 [Note] WSREP: gcomm: connecting to group ‘my\_wsrep\_cluster’, peer ‘10.10.10.31:4567,10.10.10.33:4567,10.10.10.32:456 7’ 2014-07-18 02:56:37 12539 [Warning] WSREP: (0b521a5e-0e51-11e4-b422-ee6e10b1721f, ‘tcp://0.0.0.0:4567’) address ‘tcp://10.10.10.32:4567’ points to own listening address, blacklisting 2014-07-18 02:56:38 12539 [Note] WSREP: (0b521a5e-0e51-11e4-b422-ee6e10b1721f, ‘tcp://0.0.0.0:4567’) address ‘tcp://10.10.10.32:4567’ pointing to uuid 0b521a5e-0e51-11e4-b422-ee6e10b1721f is blacklisted, skipping 2014-07-18 02:56:38 12539 [Note] WSREP: (0b521a5e-0e51-11e4-b422-ee6e10b1721f, ‘tcp://0.0.0.0:4567’) address ‘tcp://10.10.10.32:4567’ pointing to uuid 0b521a5e-0e51-11e4-b422-ee6e10b1721f is blacklisted, skipping ---
**Author:** ![MacKiller](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@MacKiller](https://forums.percona.com/u/MacKiller)\ **Post date:** [July 23, 2014, 4:36pm UTC](https://forums.percona.com/t/how-does-one-troubleshoot-a-server-crashing/3625/2 "2014-07-23T16:36:52Z")
Posted in wrong forum. Please delete. Re-asked on the right forum. Thanks