Plesk backup / mysql_dump issues after upgrade to 5.538
Posted: Mon Jul 28, 2014 11:44 am
Hi all. I'm running Plesk 11.5.30 on a dedicated (and newly configured) Cent OS 6.5 box. I've just migrated about 30 web sites from an older server, which was running Plesk 9.5.4. All software on the new server is up to date, to my knowledge. I recently upgraded to MySql 5.5.38 using the Atomic repo, and I'm getting the following errors backing up through Plesk panel, and doing mysql dumps using automysqlbackup.
Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = (databasename) Cannot load from mysql.proc. The table is probably corrupted (1548)
According to Plesk ( http://kb.parallels.com/121164 ) - i can run mysql_upgrade and it will magically fix everything. Since this is on a running production server with about 30 sites on it, I'm a little paranoid. Does anyone have any direct experience with this upgrade? Are there any potential pitfalls / issues / incompatibilities?
Also, I've already run 'mysqlcheck --all-databases --check-upgrade' and output indicates that all of my tables are OK. So what gives?
Thanks in advance -
Scott
Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = (databasename) Cannot load from mysql.proc. The table is probably corrupted (1548)
According to Plesk ( http://kb.parallels.com/121164 ) - i can run mysql_upgrade and it will magically fix everything. Since this is on a running production server with about 30 sites on it, I'm a little paranoid. Does anyone have any direct experience with this upgrade? Are there any potential pitfalls / issues / incompatibilities?
Also, I've already run 'mysqlcheck --all-databases --check-upgrade' and output indicates that all of my tables are OK. So what gives?
Thanks in advance -
Scott