• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Unreliable migration

AdrianC

Basic Pleskian
I am trying to migrate from one Plesk 12.5.30 to another same version, it fails with this sample error log:

Code:
- Subscription 'mysite.com'
|  | 
|  `- error: Failed to create subscription 'mysite.com' in target panel
|     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:
|     Command execution failed on the local server with non-zero exit code.
|     command: /usr/local/psa/bin/subscription --create mysite.com -hosting true -hst_type phys -login adobeflash -passwd '***hidden***' -ip 5.9.x.x -mail-service-ip 5.9.x.x -do-not-apply-skeleton -notify false
|     exit code: 255
|     stdout: SUCCESS: Creation of domain 'mysite.com' completed.
|   
|     stderr: [2016-05-09 18:30:56] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx_control' '--reload'] with exit code [255]
|     PHP Fatal error:  Uncaught exception 'Service_Driver_Exception' with message 'Can not reload proxy server: ' in /usr/local/psa/admin/plib/Service/Driver/Web/Proxy/Nginx.php:121
|     Stack trace:
|     #0 /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php(87): Service_Driver_Web_Proxy_Nginx->restart(false)
|     #1 /usr/local/psa/admin/plib/Template/Configuration/Applier.php(209): Template_Writer_Webserver_Abstract->restart(false)
|     #2 /usr/local/psa/admin/plib/Template/Configuration/Applier.php(109): Template_Configuration_Applier->_applyConfigurationsToServiceNode(1, Array)
|     #3 [internal function]: Template_Configuration_Applier->applyConfiguration()
|     #4
|       thrown in /usr/local/psa/admin/plib/Service/Driver/Web/Proxy/Nginx.php on line 121
|   
|     ----------------------------------------------------------------------------
|     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.
|

What is this thing ? I need to migrate 30 websites containing 18 databases, users, passwords, emails, etc.
What am I supposed to do now ?

This migration thing is very unreliable. 30 websites are offline and I am losing money while I am looking at an error log that was not supposed to be my problem.
 
I was able to move on from there but I cannot tell what fixed it.

I restarted the importing of two subscriptions that already failed but appeared (mostly blank) in my destination server, I started again, replaced them and it completed OK, then the next subscriptions transfer also completed, even deleting the initial problematic ones and importing them again worked OK.

Something else I changed was: I added the main subscription/domain , similar to s1.mysite.com , some domains had DNS records related to this "main" host name/subscription/domain.
 
Back
Top