• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Unable to migrate v11.x to 11.x

UXMichael

New Pleskian
I become an xml error in the password fields so the migration dont work. Tested with xmllint.

Is this an Bug ?

Give it a workaround ?

Greetings
 
Please be more specific. What sort of error you have exactly? How it can be reproduced? Need more details.
 
We want migrate from Linux 11.x to Linux 11.x

In pcimmlog are the error visible the SAXParse fail on the dump
We make an test with xmllint to the document and see that the <password></password> directives crashes because not allowed chars ( the password isnt a <CDATA field )

File "/usr/lib64/python2.6/xml/sax/handler.py", line 38, in fatalError
raise exception
SAXParseException: /usr/local/psa/PMM/msessions/20121108122747245/dump.xml:526:39: not well-formed (invalid token)


xmllint /usr/local/psa/PMM/msessions/20121108122747245/dump.xml
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:526: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xD6 0xCD 0x1F 0x7D </password>
^Ã}Ñ´ikÕ]æºêkJ¡N¼ò
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:</password> error : PCDATA invalid Char value 31
^Ñ´ikÕ]æºêkJ¡N¼ò
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:</password> error : PCDATA invalid Char value 31
^¼ò
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:</password> error : PCDATA invalid Char value 31
^Ñ´ikÕ]æºêkJ¡N¼ò
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:</password> error : PCDATA invalid Char value 31
^¼ò
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:</password> error : PCDATA invalid Char value 31
^Ñ´ikÕ]æºêkJ¡N¼ò
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:</password> error : PCDATA invalid Char value 31
^¼ò
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:604: parser error : PCDATA invalid Char value 31
<password type="plain">Ô\\w@5©ÈÃ$$÷ p
*±µÿ</password>
^
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:1526: parser error : PCDATA invalid Char value 26
<password type="plain">bIÈpj¼õãM</password>
^
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:1793: parser error : PCDATA invalid Char value 23
<password type="plain">Pf&gt;</password>
^
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:1793: parser error : PCDATA invalid Char value 18
<password type="plain">Pf&gt;</password>
^
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:2589: parser error : PCDATA invalid Char value 11
<password type="plain">Ô*
R¥c¦¥ÖÞ\"k#
</password>
^
/usr/local/psa/PMM/msessions/20121108122747245/dump.xml:2589: parser error : PCDATA invalid Char value 19
<password type="plain">Ô*
R¥c¦¥ÖÞ\"k#
</password>


and so on......

But we cant change all the passwords until it works

Greetings
 
Back
Top