mysql error on attempted 8.2.0 upgrade

phoenixisp · Unread post by **phoenixisp** » Sat Jul 14, 2007 3:03 pm

I am attempting to upgrade a Plesk 8.1 server to 8.2 and am getting this error:

Warning: packages conflict by files detected: package mysql-server-4.1.20-1.RHEL4.1.i386
conflict with package mysql-4.1.21-2.rhel4.art.i386
both have file /usr/share/man/man1/myisam_ftdump.1.gz with different md5 sum.

Art's is installed already. I would appreciate any guidance Scott.

Thanks
Sonny

Unread post by **scott** » Sat Jul 14, 2007 4:44 pm

up2date right?

phoenixisp · Unread post by **phoenixisp** » Sat Jul 14, 2007 5:29 pm

I'm sorry, I don't know what you mean. I did not use up2date. I am using the Plesk installer. Should I use up2date?

Here is some more of the error statement if it helps.

Can't select which of conflicting packages add to blacklist: mysql-4.1.21-2.rhel4.art.i386 or mysql-server-4.1.20-2.RHEL4.1.i386: both branches of prediction ends with fail.
Can't select which of conflicting packages add to blacklist: mysql-4.1.21-2.rhel4.art.i386 or mysql-server-4.1.20-1.RHEL4.1.i386: both branches of prediction ends with fail.
catch error with message: Installation impossible

Unread post by **scott** » Sun Jul 15, 2007 7:54 am

Ah so thats output from the psa installer huh? My guess is that its looking for a literal match on the name. I'm not maintaining the 4.x series any more, but an easy fix might be to see if there are any updates from Red Hat on mysql, hopefully the PSA installer can handle that condition. Barring that you could try installing/updating PSA through yum.

phoenixisp · Unread post by **phoenixisp** » Sun Jul 15, 2007 8:00 am

Yes sir, and it's also giving the same type of errors for Python and yum. I tried to force the 8.2.0 install and it says that 8.2.0 is installed, yet the control panel shows 8.1.1.

The biggest problem comes when I click a client or domain in the CP, I get:

MySQL query failed: Unknown column 'uid' in 'field list'

Unread post by **scott** » Mon Jul 16, 2007 10:19 am

That sounds like something failed on the mysql side during the update. You might need to roll back to an older backup (/var/lib/psa/dumps <- running 7 day backup) and try that upgrade again.

phoenixisp · Unread post by **phoenixisp** » Mon Jul 16, 2007 10:28 am

I'll give it a try. Thanks Scott.

Highland · Unread post by **Highland** » Mon Jul 16, 2007 11:11 am

When I reimaged my server at the start of the year I had to remove the ART MySQL package and let Plesk install its preferred 4.1.20. Then I upgraded to 4.1.21. Keep in mind this was a new install and ART has move to 5.0.27 as its latest package.

phoenixisp · Unread post by **phoenixisp** » Wed Jul 18, 2007 7:53 pm

Well Scott, that didn't work. I dropped the psa database and restored the oldest daily dump I had and it didn't help (or hurt) so then I tried with a dump named mysql.preupgrade.dump.gz and still no difference. Any other ideas or is this box hosed?