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

Plesk 7.5 database crash... Restore old database?

C

coh_hl

Guest
Hello,

We have a very serious problem.

Everything started with that PHP and MySQL didn't work... There was a dynamic value that Plesk didn't change that caused the crash...

We tried to upgrade plesk yesterday ( 24th of May) to the latest version, but it wasn't sucessfull.

Now the plesk database is currupt and we cannot access Plesk. There is a error message in the Web browser when we try to reach Plesk... Now we have turned off Plesk so I can't give you the error messages, but I know it's the database causing the problem (the Planet told us).

We have psa dumps from 14th of april. Do they content the Plesk database? How do I extract it ? Can you please describe what command will use? Maybe I can extract all files to a temporary folder and then copy the database back.

Thank you very much in advance.
 
I am not expert but you can try to restore psa database with the code below.

mysql -u admin -p `cat /etc/psa/.psa.shadow` psa < /path/to/database.sql

Good Luck.
 
Back
Top