• 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.

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