Back Up Error (After Update)

I have just checked out my emails and have received a notice 'Partially completed backup of Virtualmin'.

Checking the email, it seems that there are mysql errors: Dumping MySQL database .. .. dump failed! mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = ''': Cannot load from mysql.proc. The table is probably corrupted (1548)

Up until today, backup worked.

I am running MySQL version 5.5.16.

I am sure VM/WM/UM updated yesterday.

Anyone with some thoughts?



I am trying to access one of the sites and get a mysql error 'cannot connect to database'.

Looking at phpmyadmin, I see the following: !Your PHP MySQL library version 5.1.57 differs from your MySQL server version 5.5.16. This may cause unpredictable behavior.!

I will investigate this further!

Looks like this is not the issue!

Howdy -- is it possible that MySQL or PHP could have been updated from an unusual source?

It almost sounds like a non-standard MySQL or related library is on your system that could be the cause of, or at least contributing to, the problem that you're seeing.

I have Atomic included in my repos.

I seem to remember that this is for something to do with Zend.

Maybe it is a Zend related issue, as some domains work, some do not. Of the ones that do not, Joomla has issues, but other programs on the domain, do not!

I think is is related to Zend Guard.

I didn't even realize there was a PHP 5.5.x :-)

That doesn't come standard with any Linux distribution -- so that may be coming from a third party repository.

I'd suggest using caution with third party repositories on live servers :-)

I just saw your update about not seeing PHP 5.5.x packages though... what output do you get if you run this command:

rpm -qa | grep php-

I am a bit silly! I should have referred to mysql, not php!

php is at 5.3.8, but mysql is at 5.5.16.

I need to step back from 5.5.x to 5.3 (or whatever your latest version is!).

On a separate note, I have had PHP issues before, as your latest version does/did not work with Zend!


-bash-3.2# rpm -qa | grep php- wbm-php-pear-1.5-1 php-pear-1.8.0-1.el5.vm -bash-3.2#

-bash-3.2# rpm -qa | grep mysql- -bash-3.2#

Well, Virtualmin doesn't provide MySQL -- when you install Virtualmin, the MySQL version you get is the one that comes with CentOS.

Since the PHP version that comes with CentOS 5 is older, 5.1.6, Virtualmin does offer a "bleed" version of PHP for those needing a newer version -- 5.2.17. Zend should work with that though, particularly because at this point that's a bit on the older side of things.

CentOs 5.6 began offering PHP 5.3.3 for those looking for a newer PHP version.

Now, as for MySQL -- it's not as easy to go backwards as it is to go forwards :-)

MySQL will perform changes to the table structure during an upgrade -- so without a backup of your old mysql tables, I'd suggest not trying to revert to the previous version.

However, I would suggest disabling the repositories where MySQL came from, so that you don't run into issues like this again :-)

Now, as for the error you're getting now -- it looks like that may be a known bug in the upgrade to version 5.5. See if there's information in the MySQL bug report here that helps you:

I have deleted the atomic repo!

I an reading that bug report, but cant work out what the fix is! It does mention a file download, but I can't work it out!

Is there a tool named "mysql_upgrade" on your server?

According to the bug report, running mysql_upgrade may resolve the problem you're seeing by correcting the table problems.

I have previously run it, with no luck.

Also tried again, without luck!


Do you receive any output when running that?

It would normally need to be run with the -p parameter, which causes it to ask for a password.