Support

Akeeba Backup for Joomla!

#15688 Errors using Akeeba Backup with webcron and Amazons3

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 nicholas on Wednesday, 10 April 2013 02:30 CDT

Tuesday, 09 April 2013 05:51 CDT

user60737
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: (unknown)
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Akeeba Backup version: (unknown)

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
Hi,
I have followed all the instructions for using webcron to run a backup and backup to Amazons3,
I have been able to successfully backup three different sites, but i get 500 errors from the backend of the web site, and Webcron, but the backup is installed at Amazons3
The backup in Manage backups shows it has been backed up but not remotely, if i log out and log back in it shows it has been backup remotely,
There seems to inconsistencies to running the backups, the problem seems to lie with backing upto amazon,
The last test from webcron backed up the web site but it did not backup to Amazon, the backup before that one i backed up from the admin area of joomla with a 500 error but the backup installed at Amazon??
Joomla! 3.0.3 Stable
Regards
Dave

The link for the log file http://www.sunshinecoastwebdesign.com.au/log.rar
Edited by nicholas on 2013-04-09 06:10 CDT

Tuesday, 09 April 2013 08:10 CDT

nicholas
I believe these log lines tell you the entire story:
INFO |130409 06:44:58|Beginning post processing file <root>/administrator/components/com_akeeba/backup/site-www.sunshinecoastcarcentre.com.au-20130409-104327.jpa

DEBUG |130409 06:44:58|S3 -- Legacy (single part) upload of site-www.sunshinecoastcarcentre.com.au-20130409-104327.jpa

INFO |130409 06:49:51|Finished post-processing file <root>/administrator/components/com_akeeba/backup/site-www.sunshinecoastcarcentre.com.au-20130409-104327.jpa

The upload takes 4 minutes 53 seconds. This causes the timeout error to occur (500 error), but the upload is still in progress. That's also why after a while the backup appears as transferred to S3.

The only possible solutions are:
1. Use a proper command-line CRON job which is no susceptible to timeout errors
2. Use a smaller part size for split archives. Something around 10Mb should work in your case.

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!

Tuesday, 09 April 2013 15:43 CDT

user60737
Hi Nicholas,
As a matter of interest What would be a proper CRON job command line
They are now working thankyou,
I unchecked Disable multipart uploads
I checked Enable remote files quotas
Enable size quota
Size quota 10mb
Thanks
Dave


Wednesday, 10 April 2013 02:30 CDT

nicholas
Hello Dave,

Regarding your question about the proper cron command line, I would recommend going to the component's scheduling information page and take a look at the first automation method discussed at the top of this page. There is also a link to the relevant documentation page in there. Please note that this method is a little harder to set up, as it involves creating a proper cron job. Most likely you will have to ask your host to help you with this.

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!

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!