CentOS 5.5 Update breaks Plesk 8.6 DBs?

[CryoGenID]

Hello everybody!

We have just updated one of our servers to CentOS 5.5.
Before, it was running on CentOS 5.4 fine, with Plesk 8.6 (as we have Expand running here, we are stuck at Version 8.6)

The upgrade itself went smooth, found no problems so far, BUT:
If we create a new DB, that works fine. But as soon as we try to create a DB-User, we get:
"Table 'mysql.servers' doesn't exist"
Plesk cannot create a new user anymore
We have double-checked, this happened due to the "yum update".
On the "old" system, we had: Server: 5.0.90 Client: 5.0.22
When we upgrade, we get:

Code: Select all

mysql                 i386      5.1.47-1.el5.art     atomic                           4.1 M
mysql-bench        i386     5.1.47-1.el5.art     atomic                           514 k
mysql-libs             i386    5.1.47-1.el5.art     atomic                           2.1 M
mysql-server        i386     5.1.47-1.el5.art     atomic                            11 M

I have looked into another server still running on CentOS 4.5 and Plesk 8.6 and found no table "mysql.servers" there

Does anybody have a clue how I can solve this problem and get Plesk 8.6 running again AND be able
to update our servers?
The new user gets created in mysql, we can see that via mySQLAdmin, but Plesk still thinks that it couldn't create
the user and also doesn't display it in the controlpanel...

(I hope that we get Plesk 10 with a new Expand-Version soon )

Thanks a lot in advance,

best regards,

Christian

[biggles]

When you upgrade to mysql 5.1 you have to execute mysql_upgrade as root.

Code: Select all

mysql_upgrade -u admin -p your_password

[CryoGenID]

Thanks a lot for your quick reply

We just tried it out, but got a lot of messages regarding tables which needed to be updated but couldn't (as Plesk seems to use InnoDB)...
We will now try again, but this time make a DB-Dump -> Upgrade -> restore the Dump...

Are there any best-practices for this update known?

Thanks a lot again,

best regards,

Christian

[biggles]

For me, also running CentOS 5.5 and 8.6 it was just to install the update, remove/modify some obsolte code in /etc/my.conf and run the mysql-update command. then everything was up and running...

[CryoGenID]

Thanks for your reply!

Do you still remember which settings you threw out of the my.conf-file?

And did you simply ignore the errors from the update-script or did you also do that dump-restore-stuff?

Will I be needing to do the mysql-update command only for upgrades from e.g. 5.0 -> 5.1 -> 5.2 or also for minor
version numbers like 5.1.49 -> 5.1.54 ?

Thanks a lot for your help, it is very much appreciated!

Best regards,

Christian

[biggles]

I only changed the ones detailed in the log (/var/log/mysqld.log). One was removal of the line

Code: Select all

skip-bdb

edit: didn't see any errors, but there might have been some. I ignored them, (if there were any)...

[CryoGenID]

Perfect, thanks a lot

[scott]

I think it depends on the databases being used. I've had different experiences each time.

[CryoGenID]

Help

I am still getting the Plesk-Error:

Error: Connection to the database server has failed:
Table 'mysql.servers' doesn't exist

Before the update, this has worked perfectly fine...
What I did:
- Still on Server: 5.0.90 Client: 5.0.22:
- mysqldump of complete DB with --drop-database
- Upgrade with "yum update"
- Reboot Server
- Run mysql_upgrade
- Restore dump
- Run mysqlcheck -> all tables are OK

But I cannot create a new DB-user anymore (
Current phpMyAdmin-Infos: MySQL - 5.1.47, MySQL Client-Version: 5.0.22

Is that a problem that it is still the Client Version 5.0.22 ?!

Thanks a lot for any help!!!

Best regards,

Christian

UPDATE:
I just re-ran the mysql_upgrade - script (even though mysqlcheck reported everything as OK) and now it seems to work

[Highland]

Is that a problem that it is still the Client Version 5.0.22 ?!

No. The client is specific to C5. You would have to compile your own driver, which might break Plesk.

It's safe to ignore the warning.

[CryoGenID]

Thanks a lot for your reply and THANKS A LOT for everybody here in this community who helped me so quickly!

Best regards,

Christian

[laughingbuddha]

I just had the same issue on my server running CentOS 5.x 32bit and Plesk 8.6 (dare I upgrade to Plesk 9!), thankfully this thread saved my bacon. Cheers guys!

Only hit this issue when I created a new database and tried to add a database user. One question though, I have some rogue database users now due to my previous attempts to add a user for the database I created. How do I delete these users?

Thanks

[aus-city]

mysql_upgrade should be run on any upgrade of mysql versions.

[laughingbuddha]

Really, didn't know that. Never has this issue before.

[scott]

You only really needed to do that when going from 5.0 to 5.1, theres a wiki article about it here:

http://www.atomicorp.com/wiki/index.php/mysql