• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Domain Migration Fails

S

SBCTEC

Guest
I'm trying to migrate a domain from one plesk server to another. This is the error I receive:

Code:
Execution of '/usr/local/psa/bin/domuser.sh' '--update' 'domain.com' '-locale' '' failed with the return code 1.
STDOUT:

STDERR:
Wrong syntax for option's '-locale' parameter

For all intensive purposes, I'm using the latest and greatest software on both machines. Any suggestions?
 
Originally posted by SBCTEC
I'm trying to migrate a domain from one plesk server to another. This is the error I receive:

Code:
Execution of '/usr/local/psa/bin/domuser.sh' '--update' 'domain.com' '-locale' '' failed with the return code 1.
STDOUT:

STDERR:
Wrong syntax for option's '-locale' parameter

For all intensive purposes, I'm using the latest and greatest software on both machines. Any suggestions?

What the locale of domain administrator set on the source machine?
 
Originally posted by SBCTEC
I only have one locale present on each machine, en-US.

And what the locale in DB? If you look at migration Perl modules (/usr/local/psa/PMM/*.pl), it just getsl the data from the DB.
 
Both Client and Server charactersets on both servers are set to latin1.

I thought: Do I need the migration manager installed on the source server as well as the destination?
 
Originally posted by SBCTEC
Both Client and Server charactersets on both servers are set to latin1.

I thought: Do I need the migration manager installed on the source server as well as the destination?

No, you need the migration manager on the destination Plesk. If you have a look at the migration logs, you'll see migration places the migration agent on the source server and then uses only this agent as the source of migrated data exactly as it does during migration from the other hosting control panels. Also the whtole agent is available to you in the /usr/local/psa/PMM/PleskX.pl, so if you want to fix some bugs you can do this yourself. Of course, I think Plesk Migration engineers wil accept your patches/fixes with respects - they defininetly can't test Migration Manager on the all the existing configuration of software, it's very flexible and, then, usually error-prone for such a strict software as Plesk.
 
Back
Top