The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MySQL Upgrade from 5.5 to 5.6 failed

Discussion in 'Database Discussions' started by Malagana1, Feb 22, 2016.

  1. Malagana1

    Malagana1 Member

    Joined:
    Nov 25, 2015
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Mexico
    cPanel Access Level:
    Root Administrator
    Hi,

    I tried to upgrade mysql from 5.5 to 5.6 but after the upgrade process it seems that something went wrong. I have tried suggestions from similar threads, like fix rpm, removing the content from my.cnf file without any luck.

    During the upgrade process I get the following messages

    Code:
    Log Messages
    /usr/sbin/mysqld[0x593491]
    /usr/sbin/mysqld[0x59c2bd]
    /usr/sbin/mysqld[0x6ea5d1]
    /usr/sbin/mysqld[0x972d7d]
    /usr/sbin/mysqld[0xa2ad41]
    /usr/sbin/mysqld[0xaad67a]
    /usr/sbin/mysqld[0xaaba64]
    160222 20:00:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    mysql has failed. Contact your system administrator if the service does not automagically recover.
    MySQL did not start up after upgrade; there may be a problem in /etc/my.cnf. at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 800.
    
     
    #1 Malagana1, Feb 22, 2016
    Last edited by a moderator: Feb 23, 2016
  2. Malagana1

    Malagana1 Member

    Joined:
    Nov 25, 2015
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Mexico
    cPanel Access Level:
    Root Administrator
    Just for the record after a lot of time I fix the issue that seems related to corrupted innodb tables during the upgrade proccess due a customs settings in my.cnf. If you have made any changes to my.cnf it is better do a backup and remove any changes to avoid conflicts before the upgrade process is executed.

    This are the settings used to be able to run mysql service again.

    In my.cnf remove the content and put
    Code:
    innodb_force_recovery=4
    innodb_purge_threads=0
    After the change I restarted mysql service with success. The recovery mode seems to fix some errors related to the innodb databases. I removed the params from my.cnf and restarted the upgrade process with success from WHM Panel. Then I ran the following command from ssh session:

    Code:
    mysqlcheck --all-databases
    
    And all the tables seem to be OK
     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    650
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  4. kszadkowski

    kszadkowski Registered

    Joined:
    Sep 30, 2014
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Same situation, also helped:
    Code:
    innodb_force_recovery=4
    innodb_purge_threads=0
    
    Have you do something more after that to find where is bug?
     
  5. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    650
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    It's likely InnoDB is corrupted, as opposed to a bug in the upgrade process. Here's another thread you may find helpful if InnoDB is still failing:

    InnoDB Corruption Repair Guide

    Thank you.
     
Loading...

Share This Page