Support

Akeeba Solo

#23226 AJAX Loading Error. HTTP Status: 503 (Backend fetch failed)

Posted in ‘Akeeba Solo (standalone)’
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

PHP version
n/a
Akeeba Solo version
n/a

user88161
When I got 33% of the back up, I have the next error (I send u an image as well) :

El respaldo falló

La operación de respaldo se ha parado porque se detectó un error.
El último mensaje de error fue:

AJAX Loading Error
HTTP Status: 503 (Backend fetch failed)
Internal status: error
XHR ReadyState: 4
Raw server response:
Error 503 Backend fetch failed
Backend fetch failed

Guru Meditation:

XID: 1028093

Varnish cache server

Can u help? We have installed Varnish in the server.

tampe125
Akeeba Staff
Hello Carlos,

can you please attach the log of the failed backup?

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user88161
Yes of course,

tampe125
Akeeba Staff
It seems you are backing up Jotcache table record.
Can you please exclude that table records from the archive and try again?
Since it's just cached data, there is no need to during a restore

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user88161
I deleted completely jotcache (plugin and component) becouse I was not using it.
I launch again but the error message is the same.
I send u the log again.

tampe125
Akeeba Staff
it seems you have a lot of duplicated tables.
For example there is #__content_ok and #__content_frontpage_ok, please double check the table that are actually backed up.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user88161
I excluded all the duplicated tables. I attach the log.
Te error is the same:
El respaldo falló

La operación de respaldo se ha parado porque se detectó un error.
El último mensaje de error fue:

AJAX Loading Error
HTTP Status: 503 (Backend fetch failed)
Internal status: error
XHR ReadyState: 4
Raw server response:
Error 503 Backend fetch failed
Backend fetch failed

Guru Meditation:

XID: 624087

Varnish cache server

Por favor pulse en el botón de 'Ver Registro'en la barra de herramientas para ver el fichero de registro de Akeeba Backup para más información.

tampe125
Akeeba Staff
It seems that the backup gets killed before it can run another step.
Please try to run the configuration wizard again and then take another backup. The wizard will try to understand what's the optimal execution time.
If you still get a backup error, please try to manually set these values inside the configuration page:
Maximum execution time: 3 seconds
Minimum execution time: 5 seconds
Runtime bias: 75

Yes, minimum is greater than the maximum, that's not a typo
Backup speed will be lowered, but you should avoid timeout issues.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user88161
Ok, finally I got the backup. However, while it was running, it stopped 5 or 6 times with the same error HTTP Status: 503 (Backend fetch failed), but the back up went on every time. Is that ok? I send u the log again. It is 12 MB size.

user88161
Ok, finally I got the backup. However, while it was running, it stopped 5 or 6 times with the same error HTTP Status: 503 (Backend fetch failed), but the back up went on every time. Is that ok? I send u the log again. It is 12 MB size.

tampe125
Akeeba Staff
Your server is killing a backup that takes too long.
Let's try to tweak it and backup only the useful stuff.
First of all I can see you are backing up sh404sef url cache table; you can exclude it.
Then in the scanner engine, use the option Large site scanner.

This should help, if not please post here and we will try another workaround

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.