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

pleskrestore and domain with a large database filling /tmp 100%

H

Holger Korsch

Guest
Hi,
I am using pleskrestore to migrate domains.
Everything is running fine, but for a domain with a very large database it is not working as /tmp is getting 100% full during unpacking:
/tmp/migration-unpack-9zIcSs

I already set /tmp to 4Gbyte, but for this domain I need minimum 12Gbyte or even more. Is it possible to tell pleskrestore to use another path for /tmp ?


Here is the error-code I am getting during migration:
<?xml version="1.0"?>
<execution-result status="success">
<object name="*****.de" type="domain">
<message code="FailedDatabaseDeployment" severity="error">
<context>virtual void plesk:: DatabaseDeployer::act(plesk::XmlNode) const</context>
<file>./databases.cpp</file>
<line>190</line>
<text>Failed deployment of database db_**** (domain ****.de)</text>
<message code="tRepository::StreamError" severity="error"><text>Archiver error: from /srv/lib/psa/dumps/domains/*****.de/databases/db_*****/converted_db_*****_sqldump_0903211509.tgz to /tmp/migration-unpack-9zIcSs:
</text>
</message>

</message>
</object>
</execution-result>

any idea how to solve this problem ?
At the moment I am trying to change the responsible script for unpacking, but until now I did not find it.


many thanks
Holger
 
Hello,

I'm running into the same problem! Have you resolved this problem?

Best regards
Andreas
 
Back
Top