• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Quick question - How do I roll-back Plesk RPMs?

D

DeanW

Guest
I had a database error when upgrading between 6.0.2 and 7.5.2, but the RPMs were all installed... so the system doesn't work.

I need to install 6.0.2 fresh and restore my psabackup.

Is this as simple as rpm -e psa7.5.2* rpm and installing psa6.0.2 again, then restore?

Thanks
 
This might help..... I take no responability.... Make sure you bust out the old 6.x rpms... Hope this helps.......

As desirable as an automated rollback of RPMs is, RPM has not supported this option until recently. To be fair, RPM has supported downgrading a set of packages. For instance, if you upgraded some RPM foo-1-1 to the version foo-1-2, you could use the --oldpackage switch with the rpm command to downgrade to a previous version; like this:

# rpm -Uvh --oldpackage foo-1-1.i386.rpm
Preparing... ################# [100%]
Upgrading...
1:foo ################# [100%]
 
Got it sorted now. Uninstalled all PSA RPMs and did a fresh install of 6, restored my backup. Still failing on upgrade to 7.5.2 though..

Thanks for the tips.
 
what OS you using? All you are getting is a database error when you upgrade, but everything else works fine??


-poke
 
Hi there!

try to upgrade the server to Plesk 7 first and then continue with Plesk 7.1 Reloaded and 7.5 Reloaded in order. This way is much safer..
 
Back
Top