Upgrading MySQL 5.1 to 5.6 service failed to start

by

Recently I got the system which has MySQL server version 5.1 was running. It was good chance for me to reproduce the issue and show practical answer on question asked on stackoverflow.

Operating System: CentOS 6.5
Arch : x86_54

Symptom MySQL service failed to start after upgrading from MySQL 5.1 to 5.6 version.

Given below is the error found after upgrading to MySQL server version 5.6 from 5.1. You can get the below error in MySQL error log file.

2014-11-29 02:22:56 2175 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2014-11-29 02:22:56 2175 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2014-11-29 02:22:56 2175 [ERROR] Plugin ‘InnoDB’ init function returned error.
2014-11-29 02:22:56 2175 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2014-11-29 02:22:56 2175 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-11-29 02:22:56 2175 [ERROR] Aborting

Solution :

To solve this problem add the below given line in /etc/my.cnf file inside [mysqld] block.

innodb_data_file_path = ibdata1:10M:autoextend

Now restart the mysql service.

service mysqld restart

I hope the issue is resolved for you also.

Reference taken from MySQL knowledge base.

Related posts:

  1. SELINUX : squid service failed to start/restart
  2. Find mysql commands history without mysql server login
  3. check_openerp nagios plugin for openerp service check
  4. Prevent starting service after package installation on Ubuntu / Debian
  5. How to start / stop / restart / reload iptables on CentOS 7 / RHEL 7
  6. lock user login after failed login attempts in Red Hat 6.x and CentOS 6.x
  7. ClamAV-clamd av-scanner FAILED: CODE(0x2286dd0)
  8. error command ‘gcc’ failed with exit status 1 in Ubuntu
  9. php 5.5 APC : ERROR: `make’ failed
  10. VirtualBox Error: Failed to open/create the internal network

12 thoughts on “Upgrading MySQL 5.1 to 5.6 service failed to start”

  5. I wanted to upgrade MySQL 5.1.6 to 5.6 is this the better option or going to 5.5 is the one to proceed with. I have a MySQL version with around 10 huge DB and thinking of creating an instance of MySQL version on the same server and try the testing and upgrades on it.

    If everything goes well, replicating the same on the live MySQL version. Let me know your thoughts on it and just to inform that I have CentOS 6.x version installed and wanted to upgrade on this platform.

    • Hello Palash,

      It is good to proceed for up-gradation 5.1 > 5.6 > 5.7 . You have to make sure the application is compatible with the Database.
      I will strongly advise you to read the release notes of MySQL version 5.1,5.6 and 5.7 to know the difference between them. You have to find out in which area of DB you should be careful.
      Hence, perform the testing in staging server and never forget to take the latest DB backup.

      Regards
      Sharad

Comments are closed.