Uploaded image for project: 'Percona XtraDB Cluster'
  1. Percona XtraDB Cluster
  2. PXC-1306

LP #1152565: Segfault in gcache::RingBuffer::get_new_buffer()



    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:


      **Reported in Launchpad by Tomasz Klekot last update 09-05-2014 05:44:09

      I noticed that out of nowhere, our cluster shrinked from 3 servers to 2 servers. Seems like one of our nodes crashed approx 2 hours after it synced with the rest of the cluster(the servers runs in GMT+2 tz).
      The server was not overloaded and has plenty pf memory:

      1. free -m
        total used free shared buffers cached
        Mem: 15922 12086 3836 0 129 6459
        -/+ buffers/cache: 5497 10425
        Swap: 1952 132 1820

      The server did not face any kind of performance issues, just crashed.

      130307 22:09:35 [Note] WSREP: sst_donor_thread signaled with 0
      130307 22:09:35 [Note] WSREP: Flushing tables for SST...
      130307 22:09:35 [Note] WSREP: Provider paused at f4fc2dac-8761-11e2-0800-6accc9ba6bc6:4558
      130307 22:09:35 [Note] WSREP: Tables flushed.
      130307 22:13:04 [Note] WSREP: Provider resumed.
      130307 22:13:04 [Note] WSREP: 1 (): State transfer to 0 () complete.
      130307 22:13:04 [Note] WSREP: Shifting DONOR/DESYNCED -> JOINED (TO: 4587)
      130307 22:13:04 [Note] WSREP: Member 1 () synced with group.
      130307 22:13:04 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 4587)
      130307 22:13:04 [Note] WSREP: Synchronized with group, ready for connections
      130307 22:13:04 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      130307 22:13:08 [Note] WSREP: 0 (): State transfer from 1 () complete.
      130307 22:13:08 [Note] WSREP: Member 0 () synced with group.
      21:59:05 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/

      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 262426320 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
      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.

      We are running:
      Server version: 5.5.28-log Percona XtraDB Cluster (GPL), wsrep_23.7.r3821
      CentOS release 6.3 (Final)

        Smart Checklist




              • Assignee:
                krunal.bauskar Krunal Bauskar
                lpjirasync lpjirasync (Inactive)
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: