• 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.

Problem with migration/transfert

ErwanG

Regular Pleskian
Hello,

Since last updates, we can't make migration :

Erreur: pmm utility 'migration_handler' raised an exception. Error code is: 1
See pmmcli.log to find out detailed information on this

The errors in the file :

22785: 2012-09-25 11:43:12,444 DEBUG --> <pmmcli.MigrationGetObjectsListAction object at 0xda6110>
22785: 2012-09-25 11:43:12,444 INFO parameters: ['20120925114307959']
22785: 2012-09-25 11:43:12,444 INFO stdin: <agent-to-use>PleskX</agent-to-use>
22785: 2012-09-25 11:43:12,446 INFO Packet succesfully validated.
22785: 2012-09-25 11:43:12,447 DEBUG <pmmcli.ActionRunner object at 0xda60d0>: doActivity
22785: 2012-09-25 11:43:12,448 INFO Executing <subprocess[22786] '/usr/local/psa/admin/bin/migration-handler --migration-get-objects-list 20120925114307959'>
22785: 2012-09-25 11:45:05,900 INFO Subprocess raised ExecuteException: Subprocess <subprocess[22786] '/usr/local/psa/admin/bin/migration-handler --migration-get-objects-list 20120925114307959'> was finished with exit code 1
== STDOUT ====================
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1001</errcode>
<errmsg>Runtime error in migration handler:
&lt;class 'xml.sax._exceptions.SAXParseException'&gt; /usr/local/psa/PMM/msessions/20120925114307959/dump.xml:2035:42: not well-formed (invalid token)
Traceback (most recent call last):
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1682, in main
data_action_response, errcode_response, error_message = actions.get(sys.argv[1][2:])(parameters)
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1481, in migration_get_objects_list
return MigrationHandlerActionRunner(MigrationGetObjectsListAction, agent_to_use, migration_session_id).doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 100, in doActivity
result = self.processor.doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 344, in doActivity
objects_list_object = service.getObjectsList(self.__agent_to_use, agent_dir)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service_impl.py", line 112, in getObjectsList
objects_list = self.makeObjectsListFromDump(agent_name)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service_impl.py", line 122, in makeObjectsListFromDump
parser.parse(dump_path)
File "/usr/lib64/python2.6/xml/sax/expatreader.py", line 107, in parse
xmlreader.IncrementalParser.parse(self, source)
File "/usr/lib64/python2.6/xml/sax/xmlreader.py", line 123, in parse
self.feed(buffer)
File "/usr/lib64/python2.6/xml/sax/expatreader.py", line 211, in feed
self._err_handler.fatalError(exc)
File "/usr/lib64/python2.6/xml/sax/handler.py", line 38, in fatalError
raise exception
SAXParseException: /usr/local/psa/PMM/msessions/20120925114307959/dump.xml:2035:42: not well-formed (invalid token)
</errmsg>
</response>

== STDERR ====================

22785: 2012-09-25 11:45:05,901 CRITICAL PMMUtility exception:
Subprocess <subprocess[22786] '/usr/local/psa/admin/bin/migration-handler --migration-get-objects-list 20120925114307959'> was finished with exit code 1
== STDOUT ====================
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1001</errcode>
<errmsg>Runtime error in migration handler:
&lt;class 'xml.sax._exceptions.SAXParseException'&gt; /usr/local/psa/PMM/msessions/20120925114307959/dump.xml:2035:42: not well-formed (invalid token)
Traceback (most recent call last):
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1682, in main
data_action_response, errcode_response, error_message = actions.get(sys.argv[1][2:])(parameters)
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1481, in migration_get_objects_list
return MigrationHandlerActionRunner(MigrationGetObjectsListAction, agent_to_use, migration_session_id).doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 100, in doActivity
result = self.processor.doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 344, in doActivity
objects_list_object = service.getObjectsList(self.__agent_to_use, agent_dir)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service_impl.py", line 112, in getObjectsList
objects_list = self.makeObjectsListFromDump(agent_name)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service_impl.py", line 122, in makeObjectsListFromDump
parser.parse(dump_path)
File "/usr/lib64/python2.6/xml/sax/expatreader.py", line 107, in parse
xmlreader.IncrementalParser.parse(self, source)
File "/usr/lib64/python2.6/xml/sax/xmlreader.py", line 123, in parse
self.feed(buffer)
File "/usr/lib64/python2.6/xml/sax/expatreader.py", line 211, in feed
self._err_handler.fatalError(exc)
File "/usr/lib64/python2.6/xml/sax/handler.py", line 38, in fatalError
raise exception
SAXParseException: /usr/local/psa/PMM/msessions/20120925114307959/dump.xml:2035:42: not well-formed (invalid token)
</errmsg>
</response>

== STDERR ====================

Traceback (most recent call last):
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 2250, 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 2152, in migration_get_objects_list
return ActionRunner(MigrationGetObjectsListAction, migration_task_description, migration_session_id).doActivity()
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 156, in doActivity
result = self.processor.doActivity()
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 1661, in doActivity
return pmm_migration_handler.MigrationHandler.migrationGetObjectsList( self.__migration_session_id ,self.__agent_to_use.getValueOf_() )
File "/usr/local/psa/admin/share/pmmcli/pmm_migration_handler.py", line 211, in migrationGetObjectsList
return MigrationHandler.callMigrationHandlerWithResponse('--migration-get-objects-list', session_id = migration_session_id, input_str = agent_to_use)
File "/usr/local/psa/admin/share/pmmcli/pmm_migration_handler.py", line 511, in callMigrationHandlerWithResponse
raise PMMUtilityException('migration_handler', x)
PMMUtilityException: migration_handler was finished with exit code 1

22785: 2012-09-25 11:45:05,901 INFO Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1000</errcode>
<errmsg>pmm utility 'migration_handler' raised an exception. Error code is: 1
See pmmcli.log to find out detailed information on this</errmsg>
</response>

An idea ?
 
I think that issue caused due to presence of special symbols in the passwords for users.

==
'xml.sax._exceptions.SAXParseException'...dump.xml :2035:42: not well-formed (invalid token)
==

The above error indicates that there is parsing exception on line number 2035 and the binary symbol is 42. You can try to validate "/usr/local/psa/PMM/msessions/201209xxxxxxxxx/dump.xml" with something like:

# xmllint --schema /usr/local/psa/PMM/plesk.xsd /usr/local/psa/PMM/msessions/201209xxxxxxxxx/dump.xml --noout

Most probably you will see something like:

dump.xml:2035: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xAE 0xEF 0xF7 0xBD
<password type="plain">פui®ï÷½;óÀ]ÚHµ</password>
 
Back
Top