MySQL Upgrade from 5.5 to 5.6 failed

Malagana1

• February 22, 2016 20:29

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
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.

• 

  Malagana1

  • February 23, 2016 04:06

  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
  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:
  mysqlcheck --all-databases
  And all the tables seem to be OK

  0
• 

  cPanelMichael

  • February 23, 2016 16:52

  Hello :) I am happy to see you were able to address the issue. Thank you for updating us with the outcome.

  0
• 

  kszadkowski

  • April 05, 2016 07:14

  Same situation, also helped:
  innodb_force_recovery=4 innodb_purge_threads=0
  Have you do something more after that to find where is bug?

  0
• 

  cPanelMichael

  • April 05, 2016 14:18

  Have you do something more after that to find where is bug?

  
  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.

  0

Please sign in to leave a comment.