• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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