Article ID: 127980, created on Jan 8, 2016, last review on Jan 8, 2016

  • Applies to:
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix


  1. Backup restore from GUI stuck after IP mapping step;

  2. The following error is shown during backup restoration via cli:

    # /usr/local/psa/bin/pleskrestore --restore backup_info_*backup_number*.xml -level server
    Traceback (most recent call last):
      File "/opt/psa/admin/sbin/pmmcli", line 6, in <module>
      File "/opt/psa/admin/share/pmmcli/", line 2283, in main
        _logger.critical("PMMUtility exception: \n" +  str(unicode(e)) + "\n" +  stacktrace.stacktrace())
    UnicodeEncodeError: 'ascii' codec can't encode characters in position 1120-1124: ordinal not in range(128)
    Failed to parse response. Reason: Failed to read data from stream Process output:
  3. The following error can be found in pmmcli.log:

    PHP Warning: XMLReader::read(): /opt/psa/PMM/rsessions/*rsession_name*/dump.xml:2060: parser error : Input is not proper UTF-8, indicate encoding !
    Bytes: 0xE3 0x71 0x95 0xBC; File: /opt/psa/admin/plib/backup/Conflicts/Resolver/ConflictsResolver.php, Line: 2358


Data in /opt/psa/PMM/rsessions/*rsession_number*/dump.xml contains non-UTF8 symbols.


  1. Check /var/lib/psa/dumps/domains/*backup_number*.xml with xmllint utility:

    # cd /var/lib/psa/dumps/domains/
    # /usr/bin/xmllint --noout --schema /usr/local/psa/PMM/plesk.xsd backup_info_*backup_number*.xml

    output will be like:

     /var/lib/psa/dumps/*backup_number*.xml:851: parser error : PCDATA invalid Char value 11
  2. Replace the non-UTF8 data with UTF8 symbols i.e.:

    # iconv -f "UTF-8" -t "UTF-8" backup_info_*backup_number*.xml -o backup_info_*backup_number*-edited.xml
    # diff backup_info_*backup_number*.xml backup_info_*backup_number*-edited.xml
  3. Re-run backup restoration

Search Words

PHP Warning: fread(): 250 is not a valid stream resource

restore over cli



Failed to parse response. Reason: XML error at line 4 column 61. Error message: Invalid character Process output

Failed to read data from stream


29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f aea4cd7bfd353ad7a1341a257ad4724a 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7

Email subscription for changes to this article
Save as PDF