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

Corruption in PSA database

Steve Vos

New Pleskian
I've got some corruption on my psa database since last week, the issues started after a reseller added a subscription to the panel:


- Subscription ABC with login ABC_TLD already exists on plesk

Reseller created a new subscription XYZ with login XYZ_TLD, for some reason at this point corruption occured at the psa database and the login details from both subscription ABC and XYZ are swapped, I received immidiately an error with the generation of my httpd.conf files. After a lot of investigation I fixed that issue by removing both the ABC and XYZ subscription and restored that from backup.. Issue resolved until today..

I use installatron to managy my applications, a customer A installs a new wordpress website, at the end of the installation installatron sends an email with login details to the customer, but for some reason customer A didn't receive the message but customer B. This are other customers than the ABC and XYZ subscriptions, but I guess that this is an issue related to the problem from last week and that we've curruption in the psa database.

Does someone have any idea how to check for the corruption and how to recover from the corruption? Is an upgrade to Plesk 11.5 a possible solution ?
 
Back
Top