Support

Akeeba Backup for Joomla!

#25458 FTP upload fails...

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by TheEdge2 on Thursday, 14 July 2016 22:42 CDT

TheEdge2
Hi,

I am attempting to use the FTP post processing engine to upload completed backups to https://storagemadeeasy.com/. Looking at the logs I can see that we get as far as the FTP stage but then FTP fails with no error given:

DEBUG   |160624 15:16:08|Loading post-processing engine object (ftp)
INFO    |160624 15:16:08|Initializing post-processing engine
DEBUG   |160624 15:16:08|1 files to process found
DEBUG   |160624 15:16:08|Breaking step before post-processing run
DEBUG   |160624 15:16:08|Kettenrad :: Domain object returned; propagating
DEBUG   |160624 15:16:08|Kettenrad :: Break flag status: YES
DEBUG   |160624 15:16:08|----- Finished operation 1 ------
DEBUG   |160624 15:16:08|Successful Smart algorithm on Akeeba\Engine\Core\Domain\Finalization
DEBUG   |160624 15:16:08|Kettenrad :: More work required in domain 'finale'
DEBUG   |160624 15:16:08|====== Finished Step number 29 ======
DEBUG   |160624 15:16:08|Kettenrad :: Setting the break flag between domains
DEBUG   |160624 15:16:08|*** Engine steps batching: Break flag detected.
DEBUG   |160624 15:16:08|*** Batching of engine steps finished. I will now return control to the caller.
DEBUG   |160624 15:16:08|No need to sleep; execution time: 3895.5860137939 msec; min. exec. time: 0 msec
DEBUG   |160624 15:16:08|Saving Kettenrad instance backend
DEBUG   |160624 15:16:09|Kettenrad :: Attempting to load from database (backend) [backend.id38]
DEBUG   |160624 15:16:09| -- Loaded stored Akeeba Factory (backend) [backend.id38]
DEBUG   |160624 15:16:09|====== Starting Step number 30 ======
DEBUG   |160624 15:16:09|Kettenrad :: Ticking the domain object
DEBUG   |160624 15:16:09|Akeeba\Engine\Core\Domain\Finalization::_run() Running built-in method run_post_processing
DEBUG   |160624 15:16:09|Loading post-processing engine object (ftp)
INFO    |160624 15:16:09|Beginning post processing file <root>/administrator/components/com_akeeba/backup/site-docs.mydomain.com-20160624-151441.zip
DEBUG   |160624 15:16:09|Akeeba\Engine\Postproc\Ftp:: Connecting to remote FTP
DEBUG   |160624 15:16:11|Akeeba\Engine\Postproc\Ftp:: Starting FTP upload of <root>/administrator/components/com_akeeba/backup/site-docs.mydomain.com-20160624-151441.zip
WARNING |160624 15:16:46|Failed to process file <root>/administrator/components/com_akeeba/backup/site-docs.mydomain.com-20160624-151441.zip
WARNING |160624 15:16:46|Error received from the post-processing engine:
WARNING |160624 15:16:46|Uploading <root>/administrator/components/com_akeeba/backup/site-docs.mydomain.com-20160624-151441.zip has failed.
DEBUG   |160624 15:16:46|Not removing processed file <root>/administrator/components/com_akeeba/backup/site-docs.mydomain.com-20160624-151441.zip
DEBUG   |160624 15:16:46|Kettenrad :: Domain object returned; propagating
DEBUG   |160624 15:16:46|Kettenrad :: Break flag status: no
DEBUG   |160624 15:16:46|----- Finished operation 1 ------
DEBUG   |160624 15:16:46|Successful Smart algorithm on Akeeba\Engine\Core\Domain\Finalization
DEBUG   |160624 15:16:46|Kettenrad :: More work required in domain 'finale'
DEBUG   |160624 15:16:46|====== Finished Step number 30 ======


I have tested using "Test Connection" and obviously it connects (as can also be seen by the log). Using passive or non passive makes no difference either. As I don't have access to the SME logs what is my next step? I would have expected to at least see an FTP protocol error in the Akeeba log?

nicholas
Akeeba Staff
Manager
We actually do see an FTP error in the log:
DEBUG |160624 15:16:11|Akeeba\Engine\Postproc\Ftp:: Starting FTP upload of <root>/administrator/components/com_akeeba/backup/site-docs.mydomain.com-20160624-151441.zip

WARNING |160624 15:16:46|Failed to process file <root>/administrator/components/com_akeeba/backup/site-docs.mydomain.com-20160624-151441.zip

After 30 seconds we get a response that the upload failed. This means that we started sending data to the remote server and it simply "hang up" on us after 30 seconds.

I can see three alternatives:
  • Use their WebDAV access. This is something we have actually tested and it works much better than their FTP access.
  • Use a very, very low part size for split archives (in the order of 1-5Mb). That's problematic for obvious reasons and I only include this for completeness.
  • Of course you can use a different provider, but that'd be the last resort. If you end up doing that, it's best to use Amazon S3. Cheapest, most reliable storage option out there. Second best is Dropbox. Clients also had great results with OneDrive and Google Drive but their APIs are new and I don't trust either of these two companies to keep a stable API around (they have both trashed and rewritten their API from scratch after ~2-3 years of the old API being around, without a long enough transition period).


Also note that the accounts you get from them have bandwidth limits applicable to them. The personal plan allows up to 2Gb per month, the business plan allows up to 20Gb per month. Considering that you are getting this issue towards the end of the month I have to ask you to double check whether you've gone over the limit.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

TheEdge2
WebDav has worked with Storage Made Easy so I have switched to using that.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!