Issue how to get rid of (false?) "unable to upload dump to FTP" error

[ronv]

Hi,

I'm running Plesk 12.5.30 on a Ubuntu 12.04 server and have configured daily backups to a FTP repository.

I'm getting daily error notifications, with messages like this:

Unable to upload dump to FTP, it remains in server repository and you can manually download and upload it to FTP. Upload diagnostic message: Repository error: Unable to save data to an archive. Check whether the target directory is accessible for writing. For more information, see the log file (/opt/psa/PMM/sessions/2016-07-27-031402.574/migration.log)

Yet, when inspecting the FTP repository, I see that backup files are created daily, with file sizes corresponding to the size given in the Plesk Backup Manager interface.
So, it seems that despite the error messages, the backup process does successfully complete. I'll include the migration.log file.

Is there anything I should configure differently to avoid this error? (I have configured the FTP backup task to use a passive connection after connection problems in the past)

Best,

Ron

 

[IgorG]

There are following errors in your log:

[2016-07-27 04:33:16.438|16287] INFO: Trying to resume upload...
[2016-07-27 04:33:16.680|16287] INFO: Error 55 Failed sending data to the peer
[2016-07-27 04:33:21.681|16287] INFO: Trying to resume upload...
[2016-07-27 04:33:22.126|16287] INFO: Error 55 Failed sending data to the peer
[2016-07-27 04:33:27.127|16287] INFO: Trying to resume upload...
[2016-07-27 04:33:27.369|16287] INFO: Error 55 Failed sending data to the peer
[2016-07-27 04:33:32.369|16287] INFO: Trying to resume upload...
[2016-07-27 04:33:32.884|16287] INFO: Error 55 Failed sending data to the peer
[2016-07-27 04:33:37.884|16287] INFO: Trying to resume upload...
[2016-07-27 04:33:38.120|16287] INFO: Error 55 Failed sending data to the peer
[2016-07-27 04:33:38.120|16287] INFO: Data sending interrupted, because of lost connection to FTP
[2016-07-27 04:33:38.139|16287] INFO: The utility executed with the return code: -1
[2016-07-27 04:33:38.206|16287] INFO: RepositoryError[6d2a68e3-15d4-4790-860b-6ead0f4de285]: Repository error: Unable to save data to an archive. Check whether the target directory is accessible for writing. For more information, see the log file (/opt/psa/PMM/sessions/2016-07-27-031402.574/migration.log) [:-87479937]

Make sure that there are correct permissions on ftp side.

 

[ronv]

Thanks, but when inspecting the FTP repository after such a failure notification, I do see the backup file there. I've just tried with a custom backup task to the FTP repository, which succeeded as well; also, removing that backup via the Plesk Backup Manager removed the file on the FTP repository. So it seems that permissions are allright.

Yet, I noticed how in the Plesk Backup Manager, each scheduled backup task seems to generate two entries, one of which always fails. As you can see in the screenshot attached, one of them indicates that the file is successfully uploaded to FTP (the ones with the icon in the "System notes" column). The ones without that icon report the error mentioned in my original post.

Any idea what could explain these double entries?

 

[ronv]

I've deleted and re-created the scheduled task, and the situation remains unchanged:

• I receive daily emails about failed FTP uploads
• Yet, the backup files do end up at the FTP server
• Still, my file system gets cluttered with backup dumps that aren't deleted due to the error message.

If it were just for the error messages, I could live with those (and set up an email filter), but the fact that these backup files aren't deleted is bothering me more.

Any ideas?

Best,

Ron

 

[Bitpalast]

Have you checked the FTP server's settings that you are transferring to? Maybe the timeout settings are too short for big files, e.g. in ProFTPD see TimeoutNoTransfer, TimeoutStalled and TimeoutIdle settings.

 

[ronv]

Thanks for your suggestion. It has taken some time to check, but I think disk space could have been the issue. After having deleted all backups from the FTP repository, it has filled again with daily backups without errors. Only when the disk space limit got in sight (though there still was enough space available), errors started popping up again. I have now configured the backup manager to store one less backup file, and the errors are gone.