Support

Akeeba Backup for Joomla!

#26733 Incorrect header codes on front end Akeeba backup checks

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 on Friday, 13 January 2017 17:17 CST

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


We use webcron to run the front-end backup checks on the Akeeba backups. It looks like the system is returning a 200 code which webcron inteprets as being ok.

We only get failures on webcron when the Akeeba system (or the website more likely) doesnt respond.

Is this intended to work this way? I had thought the system would have only returned the 200 code when the backups have been successful and a different code when not.

If I have mis-understood how to implement the front-end backup checks, sorry, and could you let me know how we could set up the system to be notified of unsuccessful backups.

Thanks

nicholas
Akeeba Staff
Manager
Yes, this is intended to work that way. Remember, it's the legacy front-end backup method. Full support for warning and error reporting is only possible when you're using the remote JSON API for taking backups.

The legacy front-end backup method replies only on redirections. The final redirection leads to a page that returns HTTP 200 OK unless there is a PHP or server error. This allows you to check whether your server completed the backup process. The body of this last page load is plain text, begins with a three digit numeric code followed by a space and some text. The three digit code is 200 if the backup completes successfully or 500 if a catchable backup time error occurs.

That said, the best thing you can do is setup another CRON job for the failed backup checks (please consult the Scheduling Information page in Akeeba Backup on your site). This must run after the expected finish time of the backup. It checks the database information to find out if you have a stuck or failed backup. In this case it will email you, telling you that the backup has failed. If the backup is successful no email is sent. This operation is designed to deal with use cases like yours.

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!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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!