Problems migration Tool

[PauShee]

Hello,

We have problems with the Plesk migration tool, version 11.5.30. When trying to import a web, a second sample after mistake but the file is empty and we are unable to locate the problem.

We can help?

Thanks!

 

[abdi]

a second sample after mistake but the file is empty and we are unable to locate the problem.

By file is empty do you mean the newly migrated domain's httpdocs is empty or?

 

[PauShee]

Hi Addi,

No, the empty file is the log file of migration.

Thanks

 

[abdi]

Please provide more info, such as: you are migrating from what eversion of Plesk and the O/S of source and destination ...Lastly, how many domains are you migrating? Good reading about this subject also on the URLs below:

http://kb.parallels.com/en/113586
http://kb.parallels.com/en/9679
http://forum.parallels.com/showthread.php?110135-PLESK-migration-problem

A search also will give you several threads on this subject!

 

[PauShee]

Hello,

Migration is a single domain, in fact I've tried in different domains to ensure that the problem is not that.

The version of the OS is Centos 6.2 on both servers.

 

[abdi]

Plesk migration tool is tricky, so since it has refused, you can do a manual migration of that domain name. If you don't know how to go about it, you can PM me ..

 

[PauShee]

I read online that it is likely that migration does not work if the disk space is less than 50%

 

[PauShee]

More information pmmcli.log:

[2013-09-17 22:40:12.703|25399] CRITICAL: PMMUtility exception:
Subprocess <subprocess[25402] '/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/backup/Conflicts/Runner.php --resolve-conflicts --owner-guid=a0ac6bde-e2aa-4c67-9fbc-cfa37958ea6b --restore-specification=/usr/local/psa/PMM/rsessions/20130917224012429/dump/dump_index.xml --conflicts-description=/usr/local/psa/PMM/rsessions/20130917224012429/conflict_description --conflicts-resolution-rules=/usr/local/psa/PMM/rsessions/20130917224012429/conflict_resolution_rules --restore-specification-out=/usr/local/psa/PMM/rsessions/20130917224012429/dump --session-path=/usr/local/psa/PMM/rsessions/20130917224012429 --log=conflict-resolve.log --extension-filter-file-out=/usr/local/psa/PMM/rsessions/20130917224012429/extension_filter --mode=migration'> was finished with exit code 1
== STDOUT ====================

== STDERR ====================
Error: Database server does not exist.2013-09-17T22:40:12+02:00 ERR (3) [panel]: exception 'PleskObjectNotFoundException' with message 'Database server does not exist.' in /usr/local/psa/admin/plib/DatabaseServerManager.php:169
Stack trace:
#0 /usr/local/psa/admin/plib/DatabaseServerManager.php(235): DatabaseServerManager->getServer('3')
#1 /usr/local/psa/admin/plib/backup/Conflicts/PleskDataManager.php(549): DatabaseServerManager->getDefaultServer('postgresql')
#2 /usr/local/psa/admin/plib/backup/Conflicts/Resolver/UnfitSettingsResolver.php(347): backup_Conflicts_PleskDataManager->getDefaultDbServer('postgresql')
#3 /usr/local/psa/admin/plib/backup/Conflicts/Resolver/UnfitSettingsResolver.php(32): backup_Conflicts_Resolver_UnfitSettingsResolver->_processNonExistentDatabases(Object(DOMXPath))
#4 /usr/local/psa/admin/plib/backup/Conflicts/Resolver.php(121): backup_Conflicts_Resolver_UnfitSettingsResolver->resolve(Object(DOMDocument), 'admin')
#5 /usr/local/psa/admin/plib/backup/Conflicts/Resolver.php(73): backup_Conflicts_Resolver->_resolveConflictsInDumpPart('/usr/local/psa/...', true)
#6 /usr/local/psa/admin/plib/backup/Conflicts/ConflictsRunner.php(78): backup_Conflicts_Resolver->resolveConflicts()
#7 /usr/local/psa/admin/plib/backup/Conflicts/Runner.php(13): ConflictsRunner::run(Array)
#8 {main}


Traceback (most recent call last):
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 2491, in main
data_action_response, errcode_response, error_message = actions.get(sys.argv[1][2:])(parameters)
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 2328, in resolve_conflicts
return ActionRunner(ResolveConflictsAction, resolve_conflicts_task_description, None).doActivity()
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 164, in doActivity
result = self.processor.doActivity()
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 1595, in doActivity
rsession.resolveConflictsOnce(self.get_resolve_conflicts_task_description().get_conflict_resolution_rules())
File "/usr/local/psa/admin/share/pmmcli/pmmcli_session.py", line 590, in resolveConflictsOnce
self.__doResolveConflictsOnce(conflict_resolution_rules_object)
File "/usr/local/psa/admin/share/pmmcli/pmmcli_session.py", line 587, in __doResolveConflictsOnce
pmm_conflict_detector.ConflictResolver.run(owner_guid, self.__restore_specification, self.__conflict_description, stored_conflict_resolution_rules, self.__session_path, self.__dump_index, self.__session_dump_path, self.__extension_filter_file, self.get_restore_mode())
File "/usr/local/psa/admin/share/pmmcli/pmm_conflict_detector.py", line 143, in run
raise PMMUtilityException('Conflict Resolver', x)
PMMUtilityException: Conflict Resolver was finished with exit code 1

[2013-09-17 22:40:12.704|25399] INFO: Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1000</errcode>
<errmsg>pmm utility 'Conflict Resolver' raised an exception. Error code is: 1
See pmmcli.log to find out detailed information on this</errmsg>
</response>