Support

Akeeba Backup for Joomla!

#13507 – AJAX Loading Error HTTP Status: 0 (error)

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.
Tuesday, 11 September 2012 13:30 CDT
GreggInSanDiego
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? No
Joomla! version: (unknown) 2.5
PHP version: (unknown) 5.3.14
MySQL version: (unknown) 5.0.77
Host: (optional, but it helps us help you) GoDaddy.com
Akeeba Backup version: (unknown) Pro 3.6.3

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.

File is 276 MB

hrrp://theifim.com/Akeeba-IFIM.zip

Description of my issue:
Won't complete backups. Get following error.

AJAX Loading Error HTTP Status: 0 (error)
Internal status: error
XHR ReadyState: 0
Raw server response:

Went through Troubleshooting guide:
1. Configuration Wizard used
2. PHP memory_limit 64MB
3. Configuration page and hit Save
4. "Unlimited" but only using about 2GB and GoDaddy says I am way under limit
5. No "Temporary Directory" setting found in Akeeba Backup's Configuration page.
6. Using JPA
7. Tried this, didn't work

Within the site are SugarCE, which had no problems with backups. And just added idevaffiliate, which may be cause of backup problem. Akeeba Backup didn't work after install except for 1 time where I got a complete backup. The idevaffiliate folder is about 31MB.

I don't know how to read the log to determine cause of backup.

Nickolas, you have great products. Much appreciated.
Tuesday, 11 September 2012 15:06 CDT
nicholas
Can you please ZIP and attach the backup log file? I don't want the failed backup archive (which you seem to have linked to above), I want the log file. In order to obtain that, please go to Akeeba Backup, View Log, select the Back-end origin, click on Download log file, then ZIP the downloaded .txt file and attach it to your next reply. It will help me understand what is going on.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



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



Tuesday, 11 September 2012 15:32 CDT
GreggInSanDiego
Log attached
Tuesday, 11 September 2012 15:51 CDT
GreggInSanDiego
It's been a long day. Sorry about misunderstanding the directions. The log file in zip format attached.
Wednesday, 12 September 2012 03:04 CDT
nicholas
Sorry for the delayed reply. I saw your email yesterday night but my brain was too fried to let me write a sensible reply.

I actually don't see any problem in the backup. It seems that either your network connection was lost or your host killed the backup.

If you are on a wireless connection (Wi-Fi, 3G) please try using a wired connection. I've seen all crazy things happening, from microwave ovens killing a Wi-Fi connection long enough to trigger a backup error to 3G connections showing as connected but intermittently transferring no data for quite a while. Nothing beats the stability of a wired connection, unfortunately. Also make sure your computer doesn't go to sleep.

If this doesn't help (which is the most likely outcome) then we're just witnessing another round of GoDaddy screwing up sites, like they always do... GoDaddy will kill off PHP scripts, like the backup script, if they consume too much CPU-seconds over a finite period of time. The problem is that their servers are so abysmally slow and overcrowded that this limit does get met when backing up sites, but not always. It depends on the activity of the rest of the sites on the server. One way to work around that is having the backup script do a small amount of work, wait without doing anything for a long time and so on. This will make the backup slower than a snail caught on molasses but has the potential to work. In order to do that, try the following configuration settings in Akeeba Backup:
- Minimum execution time: 7 seconds
- Maximum execution time: 3 seconds (yes, the maximum is less than the minimum, this is not a typo)
- Runtime bias: 50%

My suggestion: please migrate your sites to a real host. GoDaddy is an overpriced, underperforming, overcrowded joke of a host – and a target for hacker groups due to their stance against the freedom of speech in Internet (as witnessed by the last DNS blackout a few days ago).


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



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



Wednesday, 12 September 2012 15:10 CDT
GreggInSanDiego
I talked to GoDaddy (whom I have to stick with for now, bosses), and they said the limits might be in the php5.ini file. If that makes sense, what settings should I change?

The only thing that would make sense to me would be these:

;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 120 ; Maximum amount of time each script may spend parsing request data
memory_limit = 64M ; Maximum amount of memory a script may consume (8MB)

The actual site is about 210MB in size. Database backs up fine, seems to go till near the end before throwing an error. Attaching latest log file.
Wednesday, 12 September 2012 15:23 CDT
nicholas
No, there is no such thing in the php.ini. PHP doesn't have such an option.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



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



Wednesday, 12 September 2012 15:23 CDT
nicholas
I mean: PHP doesn't have such an option built in by default. There are third party patches and CGI wrappers which impose CPU usage limits. These are not controlled by php.ini.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



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



This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

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!