• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Error updating, not sure how to correct

T

themancan@

Guest
Hi all.
I have Plesk 7.5.2 on SUSE linux (7.5.2-suse9.1.build75050128.10) and I'm getting the following error when trying to update to 7.5.3 or 7.5.4:

----- begin of output -----
Installing mysql-client-4.0.18-32.i586.rpm
file /usr/bin/perror from install of mysql-client-4.0.18-32 conflicts with file from package MySQL-server-4.1.9-0
file /usr/bin/replace from install of mysql-client-4.0.18-32 conflicts with file from package MySQL-server-4.1.9-0
file /usr/share/man/man1/perror.1.gz from install of mysql-client-4.0.18-32 conflicts with file from package MySQL-server-4.1.9-0
file /usr/share/man/man1/replace.1.gz from install of mysql-client-4.0.18-32 conflicts with file from package MySQL-server-4.1.9-0
----- end of output -----

A while back I manually upgraded phpMyAdmin (this was obviously before I figured out that there were better ways to upgrade from within Plesk, I know it was dumb), but I've switched it back to how it was and it doesn't seem to help. It looks like the error is referring to MySQL, but I didn't touch the MySQL installation, so I'm confused.

Any ideas or expertise from somebody who actually knows what they're doing?

Thanks!
-Brett
 
Thanks for the answer. I've never done an rpm before, but the -e is to erase MySQL? This may be a really stupid question, but will this get rid of all my existing database? (That would be bad.)

If that's the only way to fix this, is there an easy way to do a complete backup of every database on my server, then restore them as they were (users and all)?

Thanks again for your help. I've spent hours on Google trying to figure this out but haven't made much progress. It is greatly appreciated.
 
Back
Top