MySQL not Starting after Upgrade to 5.5.1

[danielgaraventa_ats]

Hello,

I upgraded to 5.5.1 from 5.4.13 and after the upgrade it said it failed and to try the upgrade manually when I rebooted the server mySQL fails to start now with the error unknown variable 'innodb_file_per_table=1. I am not sure how to proceed. I did take a snapshot of the VM pre upgrade so I can revert it if need be.

[jomann]

What operating system are you running on?

It may also be that the configuration file (/etc/my.cnf) wasn't updated properly, the inonodb_file_per_table=1 should be set underneath the [mysqld] heading, and if it somehow got set under a different heading you'll need to move it under there for it to work properly.

If moving it to the right spot doesn't work you can also remove the inonodb_file_per_table variable from your mysql configuration, although that could cause problems later on if you have a lot of checks.

Once you change the config, restart mysql.

[danielgaraventa_ats]

Hello Jomann,

We are on Centos 6. I will give that a try and get back to you.

[danielgaraventa_ats]

This was my my.cnf file

Code: Select all

[mysqld]
innodb_file_per_table=1

ignore-builtin-innodb
default-storage-engine = myisam
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
query-cache-size = 10M
query-cache-limit = 70M
join-buffer-size = 512K
tmp-table-size = 20M
max-heap-table-size = 20M
thread-cache-size = 4
table-open-cache = 7168
max-connections = 250
wait-timeout = 20000
interactive-timeout = 20000

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

I commented out innodb_file_per_table=1 and mysql was able to start but if we have over 3000 services I would like to see if it would be possible to figure out why that's making mysql fail.

[jomann]

Can you do a yum info mysql and let us know what version of MySQL you are running? I expect this may be an issue with the configuraiton variables, it may not be the correct variable for your version.

[danielgaraventa_ats]

Here is my version or mySQL

Code: Select all

Installed Packages
Name        : mysql
Arch        : x86_64
Version     : 5.1.73
Release     : 8.el6_8
Size        : 2.4 M
Repo        : installed
From repo   : updates
Summary     : MySQL client programs and shared libraries
URL         : http://www.mysql.com
License     : GPLv2 with exceptions
Description : MySQL is a multi-user, multi-threaded SQL database server. MySQL
            : is a client/server implementation consisting of a server daemon
            : (mysqld) and many different client programs and libraries. The
            : base package contains the standard MySQL client programs and
            : generic MySQL files.

[jomann]

It looks like the option ignore-builtin-innodb is what is causing the problem. It does not allow for innodb tables. By default some of our new tables were innodb. You can check to verify but I assume that based on your MySQL configuration it generated the new tables that we created as MyISAM so you should have no problem just leaving out the innodb_file_per_table=1 line. It was a one time change that won't be re-added on future upgrades.

[danielgaraventa_ats]

Thanks Jomann,

I'll keep it out for now and let our server run for a while and see how it does.

[jomann]

Great let us know if you have any other issues, if not, can we close the thread?

[danielgaraventa_ats]

Jomann,

Feel free to close this thread.

Thanks for your help,

Daniel