• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Does anyone have a clue how to resolve this?

Colonel36

Basic Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
Plesk Obsidian18.0.57
I'm afraid I'm not that learned with these matters and any help whatsoever would be greatly appreciated. Thanks

Warning: Database "wp_6t1x6"
Unable to make database dump. Error: Failed to exec mariadb-dump: Exit code: 3: mariadb-dump: Error 1034: Index for table 'n2d3i_wpr_above_the_fold' is corrupt; try to repair it when dumping table `n2d3i_wpr_above_the_fold` at row: 0
 
The index must be removed and recreated. If this doesn't work (e.g. maybe the index cannot be removed, because it is corrupt), the whole table must be removed and recreated (from a backup peferrably).
 
Removal is easy, simply click on "phpMyAdmin" in the webspace control panel "Databases" menu, then go to the table and edit the structure. Re-creating the index should also be easy, because in phpMyAdmin you can simply do this by GUI. The only thing you'll need to know is what the index was about, e.g. what field it contains, whether they are "unique", "primary", etc.
 
It will work without the index, but accessing a table without a proper index also results in full tables scans whenever a SELECT query is brought against the table. I advise to re-create the index as it was supposed to be. This will greatly reduce the number of datasets that need to be read upon SELECTs, hence it will greatly increase the speed to query that table.
 
Thanks.
I deleted the table since it was empty. Now the table has appeared again and is populated and working fine. A great many thanks for the support!
 
Back
Top