mysql crash after upgrade from 5.1 to 5.6

  • Filter
  • Time
  • Show
Clear All
new posts

  • mysql crash after upgrade from 5.1 to 5.6

    We recently upgraded from mysql 5.1 to Percona XtraDB Cluster 5.6.19-67.0 Since then we have been seeing frequent crashes with the following output in the log:

    15:33:14 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 = 25688954 K bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    Thread pointer: 0x508c780
    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 = 7ff549ab8d38 thread_stack 0x40000
    /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3 THDPcj+0x120c)[0x6ef2bc]

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

    Any ideas as to what may be causing this?

  • #2
    An Update:
    We were seeing mysql crash every 2-20 minutes. We were using the Percona XtraDB Cluster version 5.6.19-67.0-56 as we were planning on setting up a Galera cluster in the future. We uninstalled Percona XtraDB Cluster and installed Percona Server 5.6.17-66.0 and have not seen mysql crash since. I can't say whether it was the Galera bits or the slightly newer version of mysql that was causing the problem.


    • #3
      Hi msadm,

      It's recommended when upgrading a MySQL based data set to upgrade one major version step at a time. In other words, upgrade the data from 5.1 to 5.5, then from 5.5 to 5.6. Did you follow that procedure?If not, you may need to do a mysqldump and load into a new clean table store.