• 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.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Issue Mail service creation for add-on domains fails on two different servers

Bitpalast

Plesk addicted!
Plesk Guru
After clicking "add domain", filling the form an clicking "Add domain" to start the process, all steps work until the last "Configuring mail" step:

Code:
Task is not responding: id=8981, pid=28699, type=domain-create, checkForSubscriptionSwitch=1, currentPanelSubscriptionId=280, current_stage=Mail, domainName=<add on domain name>, formValues=Array, hostingType=hosting, isNewCustomer=, isNewSubscription=, isTechnicalDomainSelected=, ownerId=1, redirect=/smb/web/view, referrer=/smb/web/add-domain, runTaskUnderLogin=admin, subformParams=Array, subscriptionId=280, successRedirectUrl=/smb/web/view, techDomainTourAvailable=1

mailmng-outgoing failed: ERROR:__main__:column guid is not unique

Seen today on two different servers, both CentOS 7.9 with latest Plesk MU. Not sure what has changed on them, because neither one was recently updated to a new Plesk version. One of the servers has been updated from MariaDB 10.1 to 10.5 ten days ago, however, we did a "plesk repair db -y" after the upgrade and during the past ten days no transactions in Plesk have failed on that server. The other server was updated from 10.1 to 10.5 two days ago, but again, "plesk repair db -y" after the upgrade was good and no other issues were encountered.

This article seems to address the issue:
but not sure why it is happening in the first place.

In this situation "plesk repair db -y" reports an issue with auto_increments that was previously not reported:
Code:
Checking the consistency of the Plesk database

  Wrong AUTO_INCREMENT values in the following tables: Parameters: 921
  ≠ 1565 ............................................................ [ERROR]
    Updating AUTO_INCREMENT values .................................. [FAILED]
    - Updating AUTO_INCREMENT failed for tables: clients, clients,
      clients
on the first execution of "plesk repair db" only. On the second execution, all is "OK" again although the first execution reports that it was unable to correct the values.

After removing the incompletely created add-on domain by the "removal" icon and re-adding the same domain by using the same "Add domain" method, everything works as expected again including mail creation.
 
The issue re-occured on another host. The previously mentioned solution from Unable to open the Mail Settings menu in Plesk interface: Permission Denied did not work, it fails as follows:

Code:
[root@...]# ./correct_mailmng.sh <domain name>
DB query failed: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1026-nonexist_mail' for key 'PRIMARY', query was: REPLACE INTO `Parameters` (`parameter`, `value`) VALUES (?, ?)

exit status 1

A "# plesk repair db -y" right afterwards did not give any errors. Removing the newly created domain and adding it again afterwards went through without any errors.

After my posts above I had "db-repaired" all hosts pre-emptively and did not see any errors. Still, I have a feeling that this is a one-off error after the MariaDB upgrade from 10.1 to 10.5, because so far I have only encountered it on the servers that have recently been upgraded, although Plesk knows about the upgrade and is displaying all components correctly and not showing any other issues. Also, after the error occurs and is resolved by removing/re-adding the domain, further "add domain" operations have not yet exposed the same error.
 
Back
Top