• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

failed upgrade... how to fix?

M

MrSmith

Guest
Upgrading PSA DB failed... where too from here?

I made a bit of a mess without realising it. Some how, the upgrade from 8.0 to 8.1 failed to upgrade the psa database. Oddly, Plesk still worked fine after this. A later attempt at upgrading to 8.1.1 upgraded mysql-server to 5.0.x but failed to upgrade the psa database complaining that the admin was 8.1.0 and the database was 8.0.1. I reloaded the 8.1.0 admin interface from backup, but don't have a recent enough backup of the database to want to roll back on that too.

Is there a mysql script that I can use to upgrade the plesk database from 8.0 to 8.1 so that I can complete the upgrade process that originally failed, and then proceed with the 8.1.1 upgrade?

Tricky I know, but its the only way I can see resolving this problem...

Any help would be greatly appreciated.

Thanks
-MrSmith
 
Re: Upgrading PSA DB failed... where too from here?

Originally posted by MrSmith
I made a bit of a mess without realising it. Some how, the upgrade from 8.0 to 8.1 failed to upgrade the psa database. Oddly, Plesk still worked fine after this.

I don't think you caused that mess. I had a situation with a number of machines when upgrading from 7.5.4 to 8.. The 7.5.4 machines apparently still had PSA database version 7.0.4 or something.

Really, the Plesk updater should make you aware of such issues.. especially before you click 'Install updates' and the updater ends up installing some Plesk 8 packages whilst keeping some Plesk 7.5 packages. It was a recipe for downtime and unhappy customers.

I only saw this problem in 7.5 -> 8.. not seen it since.

I believe Plesk support installed the older versions via RPM and then upgraded to the right version. Perhaps best to ask them.

Jacko
 
Back
Top