• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved Plesk database scheme was not upgraded completely.

Carlos Gallardo

New Pleskian
When performing Plesk 18.0.29 microupdate upgrade i got

===> Plesk database scheme upgrade has been started.
/usr/local/psa/bootstrapper/pp18.0.29-bootstrapper/db.php: line 2: ?php: No such file or directory
/usr/local/psa/bootstrapper/pp18.0.29-bootstrapper/db.php: line 3: syntax error near unexpected token `"The file {$_SERVER['SCRIPT_FILENAME']} is part of Plesk distribution. It cannot be run outside of Plesk environment.\n"'
/usr/local/psa/bootstrapper/pp18.0.29-bootstrapper/db.php: line 3: ` die("The file {$_SERVER['SCRIPT_FILENAME']} is part of Plesk distribution. It cannot be run outside of Plesk environment.\n");'

===> Plesk database scheme was not upgraded completely.
 
Try to fix it with


# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation
 
those options didnt work they trow the same error
foudn the issue, the first line of db.php required /usr/lib64/sw-engine-cli-2.29 which was zero bytes juts cloned from the repo and worked
 
those options didnt work they trow the same error
foudn the issue, the first line of db.php required /usr/lib64/sw-engine-cli-2.29 which was zero bytes juts cloned from the repo and worked

The official Plesk one or are you using one of the third party mirrors? The third party ones (looking at you OVH) seem cause more problems than they're worth.
 
Back
Top