Support

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:Website crash's when Akeeba backup pro is run, shows a http 522 error then the website becomes unresponsive for 30 minutes. I have more than 20 sites all on the same server on which Akeeba is running without an issue.

The backup always seems to fail at the point it is backing up the Kunena language packs.

The 522 error is coming from CloudFlare, one of the reasons could be resource usage. Your backup is probably using too many server resources and your host is shutting down the site. You need to talk to your host to find out if this is the case and what type of resources are causing the shut down (CPU use, MySQL queries, etc.).

It is possible to slow the backup down, that uses the same amount of resources over a longer period of time. This trick will usually avoid triggering the site shut down, but it makes the backup take more time.

Cloudflare is a CDN network which I have disabled, with the same result, the backup is still crashing the site whenever it gets to /administrator/components/com_kunena/language/xxx

This site is very small, I am running Akeeba successfully on many other sites on the same server with the same settings.

Let's adjust the timing settings of the backup and see if we can avoid the error.

Please go to your Akeeba Backup Configuration page and try setting:

Minimum execution time: 1 second
Maximum execution time: 10 seconds
Runtime bias: 75%

If this still fails please try the conservative settings:

Minimum execution time: 5 second
Maximum execution time: 3 seconds (yes, the maximum is less than the minimum, it's not a typo)
Runtime bias: 50%

Hi Dale,

The second solution fixed the problem, however I still don't understand why just this one site out of 20 on my server requires these changes, especially as it is one of the smallest, but at least it works :-)

Regards

Andy

Andy,

I can't really give you any explanation. It is possible that the server was just busy and didn't have the resources available and threw the error. Sometimes finding the fix is easier than finding the cause.

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.