Support

Akeeba Backup for Joomla!

#27247 S3 backups failing for last 3 days

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 UglyEoin on Monday, 06 March 2017 11:50 CST

Friday, 03 March 2017 13:12 CST

UglyEoin
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:

Backups to S3 Fail. I've followed the troubleshooters but I don't think any of the solutions were ever going to work. Mainly because they seem to be troubleshooting server timeout times and memory limits, and 3 days ago my S3 backups were working and automated.

Never-the-less, I followed the processes outlined here:

https://www.akeebabackup.com/documentation/troubleshooter/abamazons3.html
https://www.akeebabackup.com/support/akeeba-backup-3x/12686-ajax-errors-with-amazon-s3-backup.html
https://www.akeebabackup.com/documentation/troubleshooter/abbackup.html
https://www.akeebabackup.com/support/akeeba-backup-3x/23186-amazon-s3-cron-backup-fails.html
//

------ BEGIN OF ALICE RAW OUTPUT -----
Timeout while backing up
There is already an issue with the backup engine saving its state. Please fix it before continuing.

------ END OF ALICE RAW OUTPUT -----


Timeout while backing upError
There is already an issue with the backup engine saving its state. Please fix it before continuing.
Please try setting min execution time to 1, max execution time to 10 seconds (or if the PHP timeout is less than 10 seconds, use 75% of the PHP timeout), runtime bias 75%

//

This has only been happening for 3 days so something has changed I think. Perhaps with S3? There was a big outage in Amazon the other day.

YOU SHOULD USE THE BACKUP PROFILE AMAZON S3
Edited by UglyEoin on 2017-03-03 13:19 CST

Sunday, 05 March 2017 15:31 CST

nicholas
As you can see in the log file you have misdiagnosed the issue. Amazon S3 has nothing to do with your problem. The last log entry is
DEBUG |170303 19:09:18|Akeeba\Engine\Core\Domain\Finalization::_run() Running add-on method test_extract

The last thing it tried to do was test the backup archive for errors. That takes time. Knowing that SiteGround's servers only give you about 90 seconds before terminating the process by default I think that's your problem: the CRON job is killed while the test extraction takes place. Just uncheck the box for testing the archive integrity -which you presumably checked 3 days ago- and you should be back to normal.

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!

Monday, 06 March 2017 11:34 CST

UglyEoin
That's strange, I checked that box months ago. It is not only the CRON that is failing, a manual backup with S3 in the profile is also failing. Never the less, I shall untick that box and try again and that will prove your point and then I can go to Siteground and ask them what they changed.

Monday, 06 March 2017 11:50 CST

UglyEoin
It works without that check. Thanks.

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!