• 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 mariadb corruption

jan1001

New Pleskian
Hello, overnight mariadb crashed and can not startet, because "Database page corruption on disk or a failed
InnoDB: file read of page 5102." How can I repair the system? I dont know how to find that corrupted file.
It seems I have to delete the database files to get mariadb started, but that means the plesk database is also deleted. (I have the files from the daily plesk backup.)
What can I do now?
 
Hi UFHH01, I solved the problem already. I found a InnoDB Crash Recovery Guide mixed with my knowledge about Plesk I deleted all Databases und restore them from a database dump. At moment I look for crash reason, it seems some Plesk Autoupdate Updates was the problem.
 
Back
Top