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

Migration fails FailedSiteAppDeployment

GiulianoP

Basic Pleskian
Hi....
I try to migrate some domain from first server with Plesk 9.2.1 to second server with plesk 9.2.1.
The migrations fails with this error:

<?xml version="1.0"?>
<execution-result status="success"><object name="fifty" type="client">
<object name="virgo.com" type="domain"><object name="virgo.com" type="hosting">
<message code="FailedSiteAppDeployment" severity="error">
<context>virtual void plesk::InstalledSiteAppDeployer::act(plesk::XmlNode) const</context>
<file>./siteapps.cpp</file><line>343</line>
<text>Can not deploy site application bbclone-0.46a-1 on domain virgo.com</text>
<message code="ExecCmd::ExFailed" severity="error">
<context>void plesk::ExecCmd::reportError() const</context><file>ExecCmd.cpp</file>
<line>49</line>
<text>Execution of /opt/psa/admin/plib/api-cli/siteapp-registrar.php --register
/opt/psa/PMM/tmp/pmm-xmloR5hUO -domain virgo.com -print-id failed with return code 1
Stderr is Proper Client Application Item has not been found
</text></message></message></object>

I don't understand the problem...

any idea?

thank

Giuliano
 
Hello,

Check the migration log, as described in the Knowledge Base article

Migration fails with error "Specified key was too long; max key length is 1000 bytes"
http://kb.odin.com/en/6019

It may be the cause.

Regards,
Denis
 
Back
Top