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

Looks Bootstrap repair has been stoped.

I started bootstrapper repair of Plesk12.5

# /usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh repair
Started bootstrapper repair procedure. This may take a while.

~~~~~~~~~cut

Applying migrations from: /usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.

Then it seems like stop the command.
after 2 hours still nothing get a more repair log message.

top command,
still looks like running process as
9962 root 18 0 4836 3532 944 S 0.0 0.2 0:02.68 /bin/bash /usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh repair

17493 root 16 0 90304 28m 16m S 0.0 1.4 0:17.35 /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/plib/Upgrade/upgrade.php --repair

It should be wait untill finished or any way for fixing this issue?

Thank you for your advice.
 
Thank your for your advice, IgorG.
Still I am waiting a progress after "===> Plesk database scheme upgrade has been completed."
I am going to try the repair command like "Plesk repair all"
It will be ok kill the command "/bin/bash /usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh repair" and related command by "kill-9 PID" then start the command?

Thank you.
 
Back
Top