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


      **Reported in Launchpad by Dan Rogers last update 11-03-2013 14:46:11

      While in the process of switching a database server from Percona Server 5.5.28-rel29 (in a master-master relationship) to Percona XtraDB Cluster, I encountered a situation where any attempt to start the slave on the Cluster server would cause a SEGV.

      A similar (or possibly identical) crash was reported as part of back in September.

      As with the above report, the only way to get past that point in the binlogs was to switch back to the base Percona server version.

      We've also seen 4.5 million "WSREP: skipping FK key append" messages, as described in

      Here's the dump from the logs. Config file is attached.

      121108 12:24:45 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.002763' at position 84270110, relay log '/mysqlroot/mysql/relaylog/relay.000270' position: 84270256
      121108 12:24:45 [Note] Slave I/O thread: connected to master '',replication started in log 'mysql-bin.002764' at position 402960631
      18:24:45 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

      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1945858 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x8fd29400
      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 = 7fcf47cb6e58 thread_stack 0x40000

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

      You may download the Percona Server operations manual by visiting You may find information
      in the manual which will help you identify the cause of the crash.

        Smart Checklist




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


                • Created: