Upgrade from PXC 5.5 to 5.6 failed

  • Filter
  • Time
  • Show
Clear All
new posts

  • Upgrade from PXC 5.5 to 5.6 failed

    Hello all,

    I tried to upgrade PXC 5.5.34 to PXC 5.6.16 by mentioned below:

    After installing PXC 5.6 and want to start the node, an error occured:


    2014-02-15 21:15:47 22747 [Note] Server socket created on IP: '::'.
    13:15:47 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

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

    Thread pointer: 0x12981410
    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 = 7fffc542b500 thread_stack 0x20000

    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (0): is an invalid pointer


    my.cnf is in attachment

    Is there anything I missed, or something should be provided for further?

    Thanks for all your help
    Attached Files

  • #2
    Can you provide us more information about your cluster setup..? like how many nodes, OS, and on what node u performed upgrade..!?

    also post the logs from start (when you try to start mysql).

    I checked your my.cnf file, is that your full my.cnf file..? I dont see any bind-address or port or mysqld.sock path !?. if you have not specified then put those variables and try once again.


    • #3
      Stephon - did you get this upgrade working? We're about to take the 5.6.15 plunge, on Ubuntu 12.04. Any tips you can offer?
      We already have noted that wsrep_incoming addresses are blank. A Percona engineer also advised us to be wary of this bug.