• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Forwarded to devs wp-toolkit maintenance cron error: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed

burnley

Regular Pleskian
Username: burnley

TITLE

wp-toolkit maintenance cron error: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian Version 18.0.34, last updated on Mar 18, 2021 09:59 PM
CentOS Linux 7.9.2009 (Core)

PROBLEM DESCRIPTION

One specific Plesk server started to spit out the following error via cron:

---CUT HERE---
From: "(Cron Daemon)" <[email protected]>
To: [email protected]
Subject: Cron <[email protected]> /usr/local/psa/admin/bin/php
-dauto_prepend_file=sdk.php
'/usr/local/psa/admin/plib/modules/wp-toolkit/scripts/maintenance.php'
2>/dev/null
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
Precedence: bulk
X-Cron-Env: <XDG_SESSION_ID=1005566>
X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/0>
X-Cron-Env: <LANG=en_US.UTF-8>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
X-PPP-Message-ID: <[email protected]>
X-PPP-Vhost: plesk.host
Message-Id: <[email protected]>
Date: Mon, 29 Mar 2021 05:06:39 +1100 (AEDT)

SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: InstancesDomains.instanceId, InstancesDomains.domainId, query was: INSERT INTO "InstancesDomains" ("instanceId", "domainId") VALUES (?, ?)
---CUT HERE---

These are the panel.log entries before and after that event:
[2021-03-29 05:05:20.310] ERR [panel] Protocol version '1.6.3.0' is deprecated. Current protocol version is '1.6.9.1'.
[2021-03-29 05:05:20.420] ERR [panel] Protocol version '1.6.3.0' is deprecated. Current protocol version is '1.6.9.1'.
[2021-03-29 05:05:22.070] ERR [panel] Protocol version '1.6.3.0' is deprecated. Current protocol version is '1.6.9.1'.
[2021-03-29 05:05:34.826] ERR [panel] Protocol version '1.6.3.0' is deprecated. Current protocol version is '1.6.9.1'.
[2021-03-29 05:06:39.477] ERR [extension/wp-toolkit] Failed to execute maintenance: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: InstancesDomains.instanceId, InstancesDomains.domainId, query was: INSERT INTO "InstancesDomains" ("instanceId", "domainId") VALUES (?, ?)
[2021-03-29 05:39:31.639] ERR [extension/wp-toolkit] Unable to update WordPress because WordPress version 4.9.16 requires PHP version 5.6.20 or newer. Change PHP settings on the target domain to use a newer PHP version and run the update again.
[2021-03-29 05:39:31.640] ERR [extension/wp-toolkit] Unable to process auto updates for WordPress instance #3 ('Alliance Applicances'): Unable to update WordPress because WordPress version 4.9.16 requires PHP version 5.6.20 or newer. Change PHP settings on the target domain to use a newer PHP version and run the update again.

STEPS TO REPRODUCE

Don't know

ACTUAL RESULT

"Integrity constraint violation:" error

EXPECTED RESULT

No error

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
This looks like some DB inconsistency. I'd suggest you contact Plesk Support Team for fixing this directly on your server.
 
Back
Top