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

Server was accidentally shutdown on middle of upgrade process to Plesk 12.5.

Server was accidentally shutdown on middle of upgrade process to Plesk12.5.

Suddenly shutdown when it is upgrade process at

~~~~~~~~~~~ end part of log of # cat /var/log/plesk/install/plesk_12.5.30_installation.log

**** Package plesk-service-node-utilities scriptlet completed successfully.

STOP plesk-service-node-utilities-12.5.30-cos5.build1205150826.19 upgrading AT Fri Oct 16 08:39:15 JST 2015
START plesk-core-12.5.30-cos5.build1205150826.19 upgrading AT Fri Oct 16 08:39:49 JST 2015

**** Package plesk-core scriptlet completed successfully.

STOP plesk-core-12.5.30-cos5.build1205150826.19 upgrading AT Fri Oct 16 08:43:22 JST 2015
START plesk-core-12.5.30-cos5.build1205150826.19 upgrading AT Fri Oct 16 09:09:40 JST 2015

**** Package plesk-core scriptlet completed successfully.

STOP plesk-core-12.5.30-cos5.build1205150826.19 upgrading AT Fri Oct 16 09:13:45 JST 2015


~~~~~~ end of log

so I can not access to Pleask control panel, then "504 Gateway Time-out, nginx" page has shown.

It can be fix or done to upgrade to Plesk12.5 by running a following script?

"# /usr/local/psa/bootstrapper/PLESK VERSION(i dont know yet)/bootstrapper.sh repair"

or There is any way to restart upgrade process?

Thank you.
 
Hello,
First you need to yum check command, to determine what's wrong with your box.
If yum check doesn't says something critical (i.e about corrupted rpm database). You should run plesk installer and complete the upgrade. Then, if yum check will complain about duplicated packages, you need to remove duplicated packages with least version via rpm -e --nodeps --noscrps ....
Then boostrapper repair
 
Thank you for your reply, mizar.

After positng this issue, fortunately I can access Plesk12.5 Panel , Then I can see the dashboard, system overview is
Plesk version 12.5.30 and Upgrade to the version 12.5.30 is available. (attached a screenshot)


plesk12.5 dashboard.png

I run command yum check-update and nothing say critical, so Click "Install Now" would be ok or shoud be run by command line?

Thank you.
 
Back
Top