• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Migration not working, dump.xml not well formed

RobHost

Basic Pleskian
We have serious problems with migration from Plesk 12 to Plesk 12 (latest versions). The PMM dies with "not well formed" XML problems.

Unfortunately the existing KB articels did not help, as we've got this error in the dump.xml created on the source server:

Code:
# xmllint --schema /usr/local/psa/PMM/plesk.xsd dump.xml

dump.xml:63: element reseller: Schemas validity error : Element 'reseller': This element is not expected. Expected is ( reseller-info ).
dump.xml:26052: element client: Schemas validity error : Element 'client': This element is not expected. Expected is ( client-info ).
dump.xml fails to validate

Why are these elements missing in our backup and how to fix this? Thanks!
 
Try to replace the files /usr/local/psa/PMM/plesk.xsd and /usr/local/psa/PMM/restore-specification.xsd with these from attach. The same changes should be installed with MU#40, have you installed it?
 

Attachments

  • xsd.zip
    23.9 KB · Views: 1
Thanks, these files are different from the ones on our machines - see attached image. Both servers are on "12.0.18 Update #65".
 

Attachments

  • Bildschirmfoto 2015-09-18 um 13.06.06.png
    Bildschirmfoto 2015-09-18 um 13.06.06.png
    106.9 KB · Views: 3
In such case my fix should help you, although I don't know why these changes are not present on your installation
 
Thanks, xmllint works now.
Another problem is, that PMM seems to mix domainnamens and password - any idea on that? (see screenshot)
 

Attachments

  • Bildschirmfoto 2015-09-18 um 13.25.27.png
    Bildschirmfoto 2015-09-18 um 13.25.27.png
    100.8 KB · Views: 3
Never seen such behaviour. Can't imagine how is it possible.
You should check latest folder content in the /usr/local/psa/PMM/msessions to find out more information about possible issues. Pay attention to files objects_list, objects_list_raw, migration.log and also check /usr/local/psa/admin/logs/panel.log
 
Back
Top