Search results

Hello, There is some kind of pre-migration issue that stops migration. You need to check info log, which contains a path to pre-migration report, look inside the report and resolve all issues at 'error' level there. Check this thread http://talk.plesk.com/threads/unable-to-migrate.335670/ There...

Actually, Plesk Migrator uses rsync to copy web files and mail messages for Linux servers. But additionally it recreates all objects and web configuration, like addon domains, aliases, mailboxes, etc, so no manual work is required. Also, to reduce downtime, I would recommend the following...

I confirm that fair "root" user is required for migration. User with su/sudo access, even with no password access to sudo/su, is not supported by Plesk Migrator.

Have you specified "root" user's credentials of the source server when configuring Plesk Migrator? That thread could be related: http://talk.plesk.com/threads/problem-with-the-migration-tool.335717/ Also, could you please clarify what do you mean by "the other server be at the same version"...

As for me, it seems to be an issue on the target server side, regardless of the source panel and version. But the reasons are still unclear... Do you consider providing access to Odin team to investigate the issue?

That is very strange, there should be domains that you migrated, unless you removed them from the target server. Panel Migrator does not put full API requests/responses to debug.log to keep it readable: it replaces large parts of requests/responses with "...", that's why there is no closing...

The issue should be in that file, marked with 'error' title: /usr/local/psa/var/modules/panel-migrator/sessions/20151110234449/convert_report_tree.2015.11.10.23.48.35

The issue seems to be quite complex, to speed up resolution it makes sense: 1) Provide access to your target and source servers to http://talk.plesk.com/members/aleksey-filatev.174043/ from Odin team with a private conversation (click link, then "Information" tab, then "Start a Conversation")...

According to the stack trace, there should be the following in response to some of <webspace><get> requests: <mail> ... <ip_address/> ... </mail> or <mail> ... <ip_address></ip_address> ... </mail> (IP address is absent or empty) Could you check if that true, and if so -...

We investigated the dump: according to files modification time, it seems that the dump was cached from the previous version of Plesk Migrator with the bug. Try to start a completely new migration session (with "Start New Migration" button), or remove all dump files from...

1013 error is ok - that is how Plesk Migrator checks for existing domains on target, if 1013 is returned then domain does not exist yet, and so should be created. The 2nd one is what we need. I will check tomorrow what could be wrong with it and let you know.

Unfortunately no, no result again. Some details - we checked Plesk 10.x dump with Plesk 12.5 schema, and that is not correct. One more thing to try is to import dump file as backup with backup manager in Tools & Settings. There you should disable signature check and disable password protection...

Anyway, first I'd try to remove that subscription from target Plesk, try to start migration for it once more, and see if issue persists.

Unfortunately, no useful information ( Let's go further. The dump is located here: %plesk_dir%var\modules\panel-migrator\sessions\<session-dir-id>\plesk.backup.<source-id>.converted.zip You could: 1) Try to validate the dump yourself according to http://kb.odin.com/en/117208. The instruction is...

The root cause is somewhere there: =|2015-11-06_20:54:55,497|D|MT|core.workflow.runner.by_subscription||| File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/utils/xml_rpc/plesk/operator/subscription.py", line 28, in _parse_plesk_ips There should be Plesk...

There should be another stack trace a bit before. Could you please look for all stack traces in debug.log starting with "Traceback" and post them here?

First, let's try to find information about imported backup: Open command line and type there command: dir /s /b "%plesk_dir%\Backup\*WRONG*" this should list files that could help us to figure out the issue. Put contents of them here.

Thanks for clarification. Unfortunately there is no better way for GUI. But if you have many domains to migrate, it makes sense to get used to CLI. We are currently improving documentation, and soon there will be a section describing advanced IP mapping with CLI. Briefly, you could add "IPv4...

Hello, Yes, PMM was replaced with Plesk Migrator in Plesk 12.5. Here is a related discussion: http://talk.plesk.com/threads/migration-transfer-manager-missing.335372/ Here is an up-to-date documentation: http://docs.plesk.com/en-US/12.5/migration-guide/introduction/

Hello, Do I correctly understand that on the source server you have several domains hosted on shared IP address, and after migration you want to get some of them on different dedicated IP addresses? Could you please clarify the scenario? Currently, if you migrate from GUI you can map one...