• 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.

10.4.4 Backup Fails

DickenW

New Pleskian
Backups have not been working on our plesk server for some time now - either scheduled or manually started.

They spend quite a fair bit of time running, but then their status becomes 'failed'. The error report is:

<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="error" log-location="/usr/local/psa/PMM/sessions/2012-04-18-130622.339/migration.result">
<message id="a04cf6c8-6e36-4d7a-84c1-7658f3225ea4" severity="error" code="CheckDump">
<description>Unable to check dump: Could not check dump. Invalid xml response:
at /usr/local/psa/PMM/agents/PleskX/PmmCli.pm line 177
PmmCli::parseCheckDumpResult('Error: adjacent parameter is empty in \'dump-file-specificati...') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1143
main::checkDump('/var/lib/psa/dumps', '', '/usr/local/psa/PMM/sessions/2012-04-18-130622.339') called at /usr/local/psa/admin/bin/plesk_agent_manager line 670
main::__ANON__() called at /usr/local/psa/PMM/agents/shared/Error.pm line 405
eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 397
Error::subs::try('CODE(0x9cded28)', 'HASH(0x9349c88)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 679
main::perform('verbose', 4, 'owner-type', 'server', 'split-size', 'undef', 'session-path', '/usr/local/psa/PMM/sessions/2012-04-18-130622.339', 'description', ...) called at /usr/local/psa/admin/bin/plesk_agent_manager line 1217
main::__ANON__() called at /usr/local/psa/PMM/agents/shared/Error.pm line 398
eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 397
Error::subs::try('CODE(0x9bd7424)', 'HASH(0x9bd7490)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1226
main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1228.
</description>
</message>
<message id="c14939d0-31c3-4644-8d0f-48480e58e643" severity="error" code="fatal">
<description>Unable to create dump</description>
</message>
<message id="2fef6a6b-a856-45b1-8117-c8153e22f43c" severity="error" code="UtilityError">
<description>Unable to get Global settings for APS Applications (ErrorCode: 3, STDOUT:).</description>
</message>
</execution-result>

Any suggestions please?
 
Hi Igor, thanks for the pointer. Unfortunately, I am not quite certain of what I am supposed to do.

ALL the domains on the server have a webspace_id of 0 except one, which has an id of 4.

I am not certain how to use the smb_apsPackages table to set the correct webspace_id.

There are four records in that able though that have NULL registryUIDs.

So, I should DELETE those four NULL registryUID records, right?

But how do I find out what the webspace_id should be for the domains? All the domains are owned by the same user, so should they all be set to 4?
 
I would like to suggest you contact Support Team with this very complex problem related to database inconsistency.
 
Back
Top