Support

Akeeba Backup for Joomla!

#8435 AJAX Loading Error: error on backing up files

Posted in ‘Akeeba Backup for Joomla!’
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

Nobs
Hi there,

I´ve running the latest pro version (3.0.b2) and I´m nearly getting crazy with the backups.
With the latest stable of Joomlapack(2.4.1) everything works. Because of the nice Cloud features, I have updated to AkeebaPro.

I´ve two profiles. One for the DB only and one for the files and the DB. Backups from the DB are working without problems but backups from the complete system aren´t working. I´m getting an "AJAX Loading Error: error" meanwhile "Backing up files" step. I´ve tried several tips from the forum and tried several configurations - without success!!

BTW: It is a large site with about 900 MB size (DB: 35-40MB)

Here´s the log:
Backup Log

Can U help me?

THX

Nobs
Nobbi´s Net Joomla projects - www.nobbis.net

dlb
You have quite a collection there. You have every heavyweight component known to Joomla!kind. :)

What is the size of your failed backup file? Failure in that area frequently is caused by hitting a host imposed file size limit. All we would have to do is set up a split archive to bypass that. The size of the file gives me a guess as to what the limit might be. Your site isn't big enough to hit the 2 Gb file size limit for php, so that isn't the problem.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Nobs
Yes, there are a couple of extensions working on this site. :)

I´ve tried many different split archive sizes. Actually I screwed it down to 20MB but the same issue.

Now I´ve uninstalled Akeeba and reinstalled it. When I try to backup now, I got the same error as above, but in step 2.

Here´s the log:
New Log File

Thank you!

Nobs
Nobbi´s Net Joomla projects - www.nobbis.net

dlb
The second log quit much earlier than the first one did. Are you sure you have enough disk space left on your host account? I think the points where the backup stopped are too inconsistent to be a file size limit.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Nobs
Yes, there is enough disk space. I have a 10 GB account and about 8 GB are free.
Nobbi´s Net Joomla projects - www.nobbis.net

dlb
I'm going to ask Nicholas to look at this. I have successfully compiled a list of things that are not causing the problem.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Nobs
OK, thank you!

Let me know, if you need further informations or backend access.
Nobbi´s Net Joomla projects - www.nobbis.net

nicholas
Akeeba Staff
Manager
I will need backend access. It's not timeout, it's not size, the only thing I can think of is a server-side fault -- but I need to run the backup process through FireBug to make sure my hunch is right.

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!

Nobs
Hi Nicholas,

I´ve sent you a PM with all informations.

Thank you!
Nobbi´s Net Joomla projects - www.nobbis.net

nicholas
Akeeba Staff
Manager
Dear Nobs,

EUREKA!

After two hours of pulling what little hair is left on my head, I had my moment of inspiration. As Dr. House would put it "patients lie". In this case, the patient (your server) was lying all along the way. Your server claims that the timeout limit is 30 seconds. No. It always times out at 7.5 seconds. So, I just set the maximum execution time to 5 seconds, ran a backup and... SUCCESS! 857.15Mb in 5 minutes and 39 seconds :D

I would go on with my usual rant about substandard hosts, but I am too tired (2:24 a.m.) to even bother...

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!

Nobs
Hi Nicholas,

you are sooooooo GREAT!!!!

Thank you very much!

Upto now, I had no negative experiences with this shared hoster (AllInkl.com), but to suggest a script runtime of 30 seconds compared to the reality of 7.5 seconds is very hard.

I try to get a statement of them!

Thanks again Dr. House - ahhh Nicholas! ;-)

Regards

Nobs
Nobbi´s Net Joomla projects - www.nobbis.net

nicholas
Akeeba Staff
Manager
He he! I am glad it is working now!!

The 7.5 seconds may be the result of a secondary limitation imposed by your host, i.e. a CPU usage limit. Since the backup procedure is by definition very CPU intensive, it is possible that your host was killing the backup because the process was exceeding the CPU usage quota. Lowering the max execution time to 5 seconds introduces the network response delay (with 0% CPU usage) between steps more often, therefore lowers the perceived CPU usage and avoids your host killing the script. However, having a statement from your host would be much better than having me speculate ;)

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