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

backup error

A

anthonybibi

Guest
Helo!

Since my migration to Plesk 10.2 on centos 5.5 64 bits, the shedules backup give me errors. Backups appears in the interface and the restauration seems to work (i have not tested restauration off all domains) but I received this message:

"

Backup task finished.

Task was created by with guid (b190a523-1f95-4b70-ab3c-e4970d76dd53)

Creation date is: 2011-May-30 23:56:02
Task status is: error

Dump full name is: backup_info_1105302356.xml

migration.result

<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="error" log-location="/usr/local/psa/PMM/sessions/2011-05-30-235602.486/migration.result">
<message id="27d9e7ca-7517-4ccb-8d5c-a56c56577198" severity="error" code="msgtext">
<description>'undef' password passed to makePasswordNode. Set to empty</description>
</message>
<message id="0ab64266-f09c-4a9b-877e-035cf3ba3743" severity="error" code="msgtext">
<description>'undef' password passed to makePasswordNode. Set to empty</description>
</message>
<message id="6ae7188a-f281-40e7-8c79-b773ad5d7760" severity="error" code="msgtext">
<description>'undef' password passed to makePasswordNode. Set to empty</description>
</message>
<message id="542b4508-e58d-42e6-887d-3a526627daa5" severity="error" code="msgtext">
<description>'undef' password passed to makePasswordNode. Set to empty</description>
</message>
</execution-result>

"
Do you know how to resolve this error ? Thanks

Best regards
 
The reason of this problem - Plesk database inconsistency. It is very difficult to say what is wrong there without detailed investigation directly on your server. Therefore I suggest you contact Support Team.
 
Back
Top