• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk Backup: runtime error, invalid, suspendfailed

MoritzK

New Pleskian
The following quote is the main error: (E-Mail attachment: migration.result)

<?xml version="1.0" encoding="utf-8"?>
<execution-result status="error" log-location="/opt/psa/pmm/sessions/2012-01-30-230004.213/migration.result">
<message id="0313cf4f-70b7-4991-8a3b-7c5f54307efa" severity="error" code="fatal">
<description>runtime error</description>
</message>
<message id="b7c17945-c801-485d-8c0a-45a9d5d101bb" severity="error" code="checkdump">
<description>the dump have been invalidated by check-dump operation</description>
</message>
</execution-result>


This quote appears when the domains are suspended during the backup: (E-Mail attachment: migration.result)

<?xml version="1.0" encoding="utf-8"?>
<execution-result status="error" log-location="/opt/psa/pmm/sessions/2012-01-31-030043.208/migration.result">
<message id="f58d3e6f-cd7b-4c26-8fde-0bc194e1d674" severity="error" code="fatal">
<description>runtime error</description>
</message>
<message id="44813ccd-3e09-4774-8df0-0c68aa4d25ce" severity="error" code="checkdump">
<description>the dump have been invalidated by check-dump operation</description>
</message>

<object name="user1" type="client">
<object name="domain-b.de" type="domain">
<message id="9dcb74bf-d54d-4154-8dd5-bb9360a943f9" severity="warning" code="suspendfailed">
<description>the domain 'domain-b.de' was not suspended during backup!</description>
</message>
<message id="4e42004e-b628-4d06-8106-47ba3b2ce3bd" severity="error" code="utilityerror">
<description>cannot suspend domain 'domain-b.de' (errorcode: 1, stdout:turn off domain failed: Bad session type.
)
[error:]. This is not fatal error!
</description>
</message>
</object>
<object name="domain-a.de" type="domain">
<message id="cdd65c77-1e9e-4f53-80df-f0750919fa8b" severity="warning" code="suspendfailed">
<description>the domain 'domain-a.de' was not suspended during backup!</description>
</message>
<message id="77a730e3-e686-4e4c-86d4-76ee5a27305e" severity="error" code="utilityerror">
<description>cannot suspend domain 'domain-a.de' (errorcode: 1, stdout:turn off domain failed: Bad session type.
) [error:]. This is not fatal error!</description>
</message>
<object name="domain-a.de" type="hosting">
<object name="domain-c.de" type="domain">
<message id="dbf459a7-3b51-4164-84c7-5b9cddd018f7" severity="warning" code="suspendfailed">
<description>the domain 'domain-c.de' was not suspended during backup!</description>
</message>
<message id="ba5bbef5-47e4-4ce7-8190-95e2f5b07b3c" severity="error" code="utilityerror">
<description>cannot suspend domain 'domain-c.de' (errorcode: 1, stdout:turn off domain failed: Bad session type.
) [error:]. This is not fatal error!</description>
</message>
</object>
<object name="domain-d.de" type="domain">
<message id="aba1dee3-c920-4522-8e71-002e701ef4e4" severity="warning" code="suspendfailed">
<description>the domain 'domain-d.de' was not suspended during backup!</description>
</message>
<message id="7a571a6d-e564-4f79-8b5b-b9062e272e63" severity="error" code="utilityerror">
<description>cannot suspend domain 'domain-d.de' (errorcode: 1, stdout:turn off domain failed: Bad session type.
) [error:]. This is not fatal error!</description>
</message>
</object>
</object>
</object>
</object>
<object name="domain-e.de" type="domain">
<message id="43eb6a73-070c-4af2-8424-996508f79eeb" severity="warning" code="suspendfailed">
<description>the domain 'domain-e.de' was not suspended during backup!</description>
</message>
<message id="d174f16a-cfad-480c-8424-26244efaaed8" severity="error" code="utilityerror">
<description>cannot suspend domain 'domain-e.de' (errorcode: 1, stdout:turn off domain failed: Bad session type.
) [error:]. This is not fatal error!</description>
</message>
<object name="domain-e.de" type="hosting">
<object name="domain-f.de" type="domain">
<message id="8e0d1cd7-be12-4254-826a-103f03f044a9" severity="warning" code="suspendfailed">
<description>the domain 'domain-f.de' was not suspended during backup!</description>
</message>
<message id="537abf77-b564-42fe-8c81-353c946e1c30" severity="error" code="utilityerror">
<description>cannot suspend domain 'domain-f.de' (errorcode: 1, stdout:turn off domain failed: Bad session type.
) [error:]. This is not fatal error!</description>
</message>
</object>
</object>
</object>
</execution-result>

Plesk: 10.4.4 Update #14 (build1013111102.18)
Ubuntu 10.04
Linux 2.6.18-028stab092.1
 
Thanks, the session.php fixed the second suspend error.


Unfortunately the main runtime error isn't fixed yet:

<?xml version="1.0" encoding="utf-8"?>
<execution-result status="error" log-location="/opt/psa/pmm/sessions/2012-01-30-230004.213/migration.result">
<message id="0313cf4f-70b7-4991-8a3b-7c5f54307efa" severity="error" code="fatal">
<description>runtime error</description>
</message>
<message id="b7c17945-c801-485d-8c0a-45a9d5d101bb" severity="error" code="checkdump">
<description>the dump have been invalidated by check-dump operation</description>
</message>
</execution-result>
 
What sort of output following SQL query:

select * from forwarding;

?
 
Use CentOS 5.6 and have the same issue.

Automatic or manually its not relevant.

Yes the error occurs on manually and automatic backup.

In my case only the mail backup is unable: "Server/Domain configuration and content (only mail configuartion and content)"

Location:
Home>Tools & Settings>Backup Manager: Server Repository>Scheduled Backup Settings
OR
Home>Subscriptions>doman-A.de>Websites & Domains>Backup Manager: Server Repository>Scheduled Backup Settings/Back Up

Other Back Up typs are able without error on whole server side and only subscription layer:
- Server/Domain configuration
- Server/Domain configuration and content
- + All configuration and content (contains mail)
- + All configuration and content except mail
 
Same problem here: Some servers work and some of them suddenly stopped working (i.e. cannot backup mail). Using Plesk 10.4.4 with all micro-updates.

Error from psadump.log:
Runtime error: The check dump failed with code '1'. The dump can contain invalid data! at /opt/psa/admin/bin/plesk_agent_manager line 682.

I have seen users reporting similiar problems but line 682 wasn´t stated in those cases. Our hosting provider got the information from Parallels that this bug is known and will be fixed, of course without stating a date =(

Has anybody got this fixed?
 
I just received info from Parallels:
"The required code changes are performed and currently the fix is under testing, so it should be ready for Plesk 11.1 release."

I hope there will be a fix for Plesk 10, too!
 
I hope there will be a fix for Plesk 10, too!
Only most critical issues which impact a lot of customers are back ported from Plesk 11 to old Plesk versions. This issue is not recognized as most critical. Sorry.
 
Well, I wouldn´t say having no backups isn´t severe, but I guess there´s no arguing.
Can you tell us when this fix will be available?
 
Updated to Plesk 11.0.9 and the problem seems to be fixed there. At least with that first server I tested.
 
Back
Top