• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk 12.5 backup error

ulitre

New Pleskian
With a recent upgrade to Plesk 12.5, we've noticed the following error each time a Plesk backup runs as follows. The file that it references is a temporary one that created and then every 60 minutes by the plugin itself but our question is, why throw an error if the file was removed and how can we prevent Plesk from throwing this error each time? The plugin properly removes the files when it hits the removal window so why would Plesk have a problem with that?

Backup task finished on host (host)

Creation date is: 2016-Mar-16 23:11:08
Created by: Plesk administrator (type=server, guid=xxxx)
Created for: Server (type=server, id=1)
Task status is: warnings (see details in the attached file)

Dump full name is: backup_info_1603162311.xml

<?xml version="1.0" encoding="UTF-8"?>

<execution-result status="warnings" log-location="/usr/local/psa/PMM/sessions/2016-03-16-231103.204/migration.result">
<object name="server" type="server">
<object name="someclient" type="client" uuid="client#someclient">

<object name="somedomain.com" type="domain" uuid="domain#somedomain.com">
<object name="somedomain.com" type="hosting">

<message id="045bf4d8-b381-44a0-8c65-59396c5a288b" severity="warning" code="msgtext">
<description>Not all the data was backed up into /var/lib/psa/dumps/clients/someclient/domains/somedomain.com successfully. /bin/tar: httpdocs/wp-content/uploads/wpcf7_captcha/396054377.png: Cannot stat: No such file or directory
/bin/tar: httpdocs/wp-content/uploads/wpcf7_captcha/396054377.txt: Cannot stat: No such file or directory
/bin/tar: Exiting with failure status due to previous errors
</description>
</message>
</object>
</object>
</object>
</object>
</execution-result>
 
Plesk gives the list of files to pack to the /bin/tar. It's the error from the tar. Such sort of warnings could be ignored. I don't know how to workaround such behavior, exept using of file exclude list, which currently doesn't supported
 
I have that problem almost on a daily basis, which is very annoying. Would be happy if this was resolved!

<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="warnings" log-location="/opt/psa/PMM/sessions/2017-01-04-005903.321/migration.result">
<object type="server" name="server">
<object name="customer" type="client" uuid="client#customer">
<object name="customer.de" type="domain" uuid="domain#customer.de">
<message severity="warning" code="msgtext" id="b32bf08d-7841-43c5-81ab-4141b04817ea">
<description>Not all the data was backed up into /var/lib/psa/dumps/clients/customer/domains/customer.de successfully. /bin/tar: t.tews/Maildir/cur/1482238767.M199264P28207.shared1.clicksports.de,S=2618369,W=2652567\:2,S: Cannot stat: No such file or directory
/bin/tar: Exiting with failure status due to previous errors
</description>
</message>
</object>
</object>
</object>
</execution-result>
 
There is no way of resolving it. Between collecting a file list of files to backup and the actual tar process that packs the files into an archive files can be modified or deleted. If that happens, tar cannot pack the file that no longer exists and throws the error. One thing you can try is to move the backup time to an hour where traffic is low, so that files or temporary mail files are not continuously modified or created/deleted. In your specific case you could also set your mail software to not constantly updating the inbox.
 
Back
Top