• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Issue Remote Backup Failure

ayadai

New Pleskian
Server operating system version
Windows Server 2016
Plesk version and microupdate number
Version 18.0.58 Update #2
When attempting to backup the full server to Dropbox, thousands of repeated errors like this occur:

Warning: Email account "[email protected]"
ERR_READ_MESSAGE_FAILED ({0} = Inbox/xxx.MAI, {1} = Entries cannot be created while previously created entries are still open.)

Mailserver is mailenable pro. The disk rapidly fills up, then the following errors (and similar) appear:
Unable to execute post-backup action. Error: Failed to exec backup_restore_helper.exe: Exit code: 1: DB query failed: SQLSTATE[HY000]: General error: 1021 Disk full (C:\Program Files (x86)\Plesk\MySQL\Data\#sql-temptable-xxx.MAI); waiting for someone to free some space... (errno: 28 "No space left on device"), query was: DESCRIBE `clients`

Here are some screenshots of the process that results in the error:

01.png

1.5.png
02.jpg
 
"Entries cannot be created while previously created entries are still open" is a generic zip message. The situation occurs if the disk is full and no more data can be written to the archive. Make sure there is enough space on your local disks, especially on the temporary path for backups.
 
"Entries cannot be created while previously created entries are still open" is a generic zip message. The situation occurs if the disk is full and no more data can be written to the archive. Make sure there is enough space on your local disks, especially on the temporary path for backups.
You can see from the entries that as recently as last month, we were able to backup. Since then, I've opened up disk space, but the backups continue to fail. Before the current version of Obsidian was installed, the backups worked fine for years with less space than is currently available. The entire purpose of having Dropbox as a backup is that there is insufficient space on the VPS to accommodate backups. So the question now is, what has changed from Onyx to Obsidian or from the last to the current update to break this critical functionality and what can be done to restore it.
 
Sure, you are right. Anyway, the same issue does not occur with other users so it must be somehow linked to your specific environment. Did you check that you have enough disk space available before the backup starts, especially on temporary paths?
 
Sure, you are right. Anyway, the same issue does not occur with other users so it must be somehow linked to your specific environment. Did you check that you have enough disk space available before the backup starts, especially on temporary paths?
Currently, there is 45GB free out of 319; this compares to ~28GB at the time of the last successful backup and before the last update to Plesk; I opened up the additional ~17GB of space to see if we could address this issue.
 
If you are sure that enough disk space is available to temporarily store the full backup before it is uploaded to your Dropbox account, and another obvious reason why the "Entries cannot be created while previously created entries are still open" occurs, I suggest to open a ticket with Plesk support so that they can look into the issue directly on your server.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
Back
Top