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

database errors in MariaDB 10.11

johnrdorazio

Basic Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
18.0.62 #1
I recently upgraded MariaDB to v10.11. I'm not sure if this error was already present, but since I've been doing some digging in the logs since the upgrade, I've been seeing this error in `/var/log/plesk/panel.log`:

Bash:
[2024-07-09 08:06:02.975] 3152662:668cd34a3e936 ERR [extension/wp-toolkit] An error occurred during update of vulnerability database: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: Vulnerabilities.vulnerabilityId, query was: INSERT INTO "Vulnerabilities" ("vulnerabilityId", "productType", "productSlug", "productNamePremium", "title", "description", "directUrl", "affectedVersions", "cvssScore", "disclosedAt", "cve", "exploited", "fingerprint", "mitigations", "riskRank") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
[2024-07-09 08:06:02.977] 3152662:668cd34a3e936 ERR [extension/wp-toolkit] Could not update vulnerabilities database: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: Vulnerabilities.vulnerabilityId, query was: INSERT INTO "Vulnerabilities" ("vulnerabilityId", "productType", "productSlug", "productNamePremium", "title", "description", "directUrl", "affectedVersions", "cvssScore", "disclosedAt", "cve", "exploited", "fingerprint", "mitigations", "riskRank") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
 
Hi, I don't think these errors are related to the MariaDB upgrade. But they do indicate an issue with the WP toolkit vulnerability database. I recommend opening a support ticket to let our support team investigate the issue and help you to solve this issue. To sign-in to support and open a ticket go to https://support.plesk.com.

If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk: https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk
 
Back
Top