• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Corrupt dump.xml file causing migration failure

K

kkaos

Guest
Hello,

I have been unable to perform a migration from a Linux Plesk 8.1 server without complete failure. I noticed that the dump.xml file that's being created on this server during the migration contains numerous weird ^@ characters, mainly in the limit values (i.e. <limit_name="disk_space">). There are way too many of these characters for me to vi into the file and remove manually; neither the sed tool nor the search utility in vi can find these characters (i.e. searching for ^@ in vi doesn't work) in order to perform an automated replace.

How can I either fix this or work around? I appreciate any guidance offered.

Thanks,


Sean
 
Faris,

Thanks for you response; however, I tried using single quotes and double quotes, but sed won't find the ^@ characters.
 
Back
Top