Posts Tagged ‘mysql’

MySQL 5.1.x on Plesk 8.3 and later

Tuesday, August 3rd, 2010

I have upgraded MySQL to version 5.1.48 on a number of CentOS based servers running different versions of Plesk. The versions of Plesk ranged from 8.3.0 all the way to 9.3.0.

IMPORTANT: After the upgrade, run

mysql_upgrade ––user=admin ––password=`cat /etc/psa/.psa.shadow`

to ensure all the required tables for MySQL 5.1.x gets created.

I also recommend running a

mysqlcheck ––optimize ––user=admin ––password=`cat /etc/psa/.psa.shadow` ––all-databases

to optimise all databases for MySQL 5.1.x after the upgrade completes.

It goes without saying, but it is a VERY GOOD IDEA, to backup /var/lib/mysql, before you start with the upgrade process.

Please note that since MySQL 5.0.12, MySQL adheres to the SQL:2003 standard. This may potentially break some SQL statements that appears to be valid SQL statements and that worked perfectly in MySQL 4.x.

Lastly, I picked up one error with one database on one server, so far:

When clients try to access their database via “DB WebAdmin” in the Plesk control panel:

MySQL said: Documentation
Non-static method PMA_Config::isHttps() should not be called statically

The fix is simple and published at the following URLs:

Strange MySQL error

Wednesday, December 2nd, 2009

While upgrading to Plesk 9.2.3 on one of my non-production servers, the Plesk upgrade process failed with the following error:

MySQL query failed: Got error -1 from storage engine

I was stumped by this error initially, since searching on the Plesk forums and Google, did not really yield any results.

I finally stumbled across a post by Derick Ng on Planet CakePHP, in which the same problem was described. Kudos to the poster for making the information available.

Bottom line is that I used the non-production server to do an InnoDB database recovery and the MySQL server was still setting the InnoDB engine into recovery mode. While the InnoDB engine is in recovery mode, you can not add data to the InnoDB tables.

Check for innodb_force_recovery in your my.cnf