GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

How does one troubleshoot a server crashing?

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • How does one troubleshoot a server crashing?

    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)? https://bugs.launchpad.net/percona-xtradb-cluster 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 https://bugs.launchpad.net/percona-xtradb-cluster
    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
    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.
    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

  • #2
    Posted in wrong forum. Please delete. Re-asked on the right forum. Thanks

    Comment

    Working...
    X