Cannot start migration from file: Error: The source file is not a valid XML file

Refers to:

  • Plesk 12.5 for Linux
  • Plesk 11.5 for Linux

Created:

2016-11-16 12:50:08 UTC

Modified:

2016-12-21 19:20:05 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Cannot start migration from file: Error: The source file is not a valid XML file

Symptoms

On the last step of migration, the following error appears under Tools & Settings > Migration & Transfer Manager > Start new Migration > Transfer data already processed by the Migration & Transfer Agent and located on the local host when path to a dump file is specified:

Error: The source file is not a valid XML file.
If you supplied an archive file containing a backup from Plesk version 9 or later, then extract the contents of this archive, and process the extracted XML file with the converter.
If you want to convert a backup file from a Plesk version earlier than 9, then you first need to process it with the pre9-backup-convert utility, and then process the resulting file with the pre10-backup-convert utility.

The following error can be found in /usr/local/psa/PMM/logs/restore-2014-03-12-13-54-32-365/pmmcli.log :

[2014-03-12 13:54:40.431|3666] INFO: Subprocess raised ExecuteException: Subprocess <subprocess[4289] '/usr/local/psa/admin/sbin/backup_sign verify /usr/local/psa/PMM/rsessions/20140312135433421/dump/dump_object338.xml'> was finished with exit code 1
== STDOUT ====================
The XML file /usr/local/psa/PMM/rsessions/20140312135433421/dump/dump_object338.xml was not parsed successfully with the following errors:
/usr/local/psa/PMM/rsessions/20140312135433421/dump/dump_object338.xml:1673:parsererror :EntityRef: expecting ';' <password type="plain">&a&c&ltPASS;&gt</password> ^/usr/local/psa/PMM/rsessions/20140312135433421/dump/dump_object338.xml:1673:parsererror :Entity 'c' not defined <password type="plain">&a&c&ltPASS;&gt</password> ^
== STDERR ====================

Cause

Special symbols like "$gt" and "$lt" in the client's password.

Resolution

  1. Find backup file with account with bad password, some sensitive data from error output can be used, for example part of the account password: "PASS" . Go to the directory with backup files and run the find command:

    # cd /transfer/
    # find . -name '*xml' | xargs grep PASS
    ./resellers/test_reseller/clients/14/domains/example.com/backup_example.com_info_1403121141.xml: <password type="plain">&a&c&ltPASS;&gt</password>
  2. Output from the command above is the file name where information about account with bad password is stored. Its name ( backup_example.com_info_1403121141.xml ) contains domain name:

    # grep -A2 -B3 PASS ./resellers/test_reseller/clients/14/domains/example.com/backup_example.com_info_1403121141.xml
    <ftpusers>
    <ftpuser name="ftpuser1">
    <sysuser name="ftpuser1">
    <password type="plain">&a&c&ltPASS;&gt</password>
    </sysuser>
    </ftpuser>
  3. To fix the issue change password for the ftpuser under the domain example.com and perform migration from scratch, starting from step 2 in article :

    ./PleskX.pl --dump-all
Have more questions? Submit a request
Please sign in to leave a comment.