Migration fails with error: mailmng-outgoing failed: ERROR:outgoing:column name is not unique

Refers to:

  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux

Created:

2016-11-16 13:10:58 UTC

Modified:

2016-12-21 20:08:03 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Migration fails with error: mailmng-outgoing failed: ERROR:outgoing:column name is not unique

Symptoms

  1. Migration finishes with the following warning:
    Failed deployment of domain example.com
    Warning:
    Execution of /usr/local/psa/admin/plib/api-cli/domain.php --create example.com -owner user -do-not-apply-skeleton -notify false -guid 056529ff-e402-463a-aa35-f82d124c4480 -creation-date 2015-03-09 -ip 10.10.10.10 -ignore-nonexistent-options failed with return code 1. Stderr is An error occurred during domain creation: mailmng-outgoing failed: ERROR:outgoing:column name is not unique

or

    error: Failed to deploy subscription 'example.com'
Migration for that subscription is considered completely failed. No further actions are performed for it.
Migration tools tried to perform operation in 2 attempts.
----------------------------------------------------------------------------
Attempt #1 failed with the following error:
Unable to create subscription 'example.com'
----------------------------------------------------------------------------
Attempt #2 failed with the following error:
Subscription already exists on target server: most probably it was created at the previous attempt,
but migration tools are not sure if it was created correctly.
It is recommended to:
1) Resolve the original issue that caused subscription creation to fail,
delete subscription, and then run migration again.
OR
2) Ensure that created subscription is fine, or the original issue is minor,
then simply run migration for that subscription again.
  1. Subscription and user have been created, but domain has No Hosting hosting type.
    No data has been restored.

Cause

Subscription example.com already exists on the destination server in outgoing mail control database.

Resolution

  1. Remove subscription example.com from outgoing mail control database on the destination server:

    # /usr/local/psa/admin/sbin/mailmng-outgoing --remove-subscription --main-domain-name=example.com
  2. Start the migration again.

Have more questions? Submit a request
Please sign in to leave a comment.