• 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Plesk migrator fails to migrate subscriptions with addons

burnley

Regular Pleskian
CentOS 5->, Plesk 12.5.30 #59, Panel migrator 2.4.9
When I'm running the migration from cli, Plesk fails to migrate the subscriptions that have addons attached because the limits enforced by the service plan on the target server are exhausted. When I look in the destination I can see the customer & subscription created, the service plan attached, but any addon that exists on the source server is missing from the destination and has to be added manually and the migration restarted. Once the addons are manually synced the migration succeeds.
I'm not seeing this problem when running the migration from the Plesk panel, only in cli.
I'm using https://docs.plesk.com/en-US/12.5/m...m-plesk/migrating-via-the-command-line.75722/ to do the migration and the steps are:
1. Set up the ssh key based authentication

2. Generate the migration list running "plesk-migrator generate-migration-list"

3. Set up the hosting plans running "plesk-migrator deploy-hosting-plans"

4. Build the IP mapping file

5. Customize the migration list, for a failed test subscription it looks like this:

# This file specifies a list of domains and clients to be migrated.
# For each domain, you should specify a service plan, that is to be
# used when creating subscription for this domain. You should also
# specify a client, that owns the domain. Domains that are not assigned
# to a customer, will be automatically assigned to a reseller or admin
# account, depending on what you've specified earlier in this file.
#
# For each client, you should specify a reseller, that will be a vendor
# of the corresponding customer. If you do not specify a reseller,
# corresponding customer will be created under admin. For the examples
# of how to specify that, consult Plesk Migrator documentation.

# Admin subscriptions and customers
Customer: custname # Customer Name
Plan: Email Only Web Hosting
Addon Plan: 07 x Additional mail boxes
failedsubscription.com.au

6. Transfer accounts running:
plesk-migrator transfer-accounts --skip-services-checks --skip-main-node-disk-space-checks --migration-list-file /usr/local/psa/var/modules/panel-migrator/sessions/migration-session/migration-list-custom --ip-mapping-file /usr/local/psa/var/modules/panel-migrator/conf/ipmapping.conf

Any ideas?
 
Hello!
Could you please provide access to source and target servers(ssh, both) in private conversation to investigate the problem?
 
Hi Alina, thanks for replying. We can't unfortunately provide access to any of the servers. What I've done in the meantime was to retest the migration for some of the failed subscriptions from the panel and it worked every time, which makes me think the 2 methods aren't functionally the same, there's a bit of inequality there :)
The alternate approach, which will likely work better, is to run the initial server migration from the panel (takes 16hours+ anyway) then run the incrementals from cli
 
burnley, we`ve not reproduced the problem which you described on our testing environment. Without access to servers I have no chances to help you :(
 
Back
Top