Support

Akeeba Backup for Joomla!

#11408 AJAX Loading Error

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 nicholas on Tuesday, 06 March 2012 15:40 CST

Tuesday, 06 March 2012 07:01 CST

user49890
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?)? yes
Joomla! version: 1.5.23
PHP version: 5.2.17
MySQL version: 5.1.56
Host: (optional, but it helps us help you)
Akeeba Backup version: 4.0

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:

Upgraded to 4.0. Backup seemed to work on prior releases
The backup operation has been halted because an error was detected.
The last error message was:

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

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

File does not exist: /home/fjmcprog/public_html/404.shtml, referer: http://www.fjmc.org/index.php?option=com_content&view=article&id=332

Tuesday, 06 March 2012 07:39 CST

user49890
Correction Akeeba release 3.4.0

I have another instance running on the same cpanel. at 3.3.13. It runs to completion.

Tuesday, 06 March 2012 07:57 CST

nicholas
You have a gigantic ZIP file in your site's root. Looks like an old backup. Maybe you'd want to remove that first before taking a new backup?

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!

Tuesday, 06 March 2012 15:32 CST

user49890
Deleted the 1 gig file and found another as well as dropped 2 large directories. Went to completion. Not a nice way to fail. Could you generate an error message saying available space exceed.

Unfortunately the problem occurred right after the 3.4 upgrade, I was also hit by the legacy problem so I was looking for another release problem.

Tuesday, 06 March 2012 15:40 CST

nicholas
The problem is that when the host runs out of disk space, it doesn't throw a catchable error. It simply TERMINATES the script while it is writing to the disk. In order to process the error you need PHP code to be running, but PHP code stops running when the error occurs. In other words: a typical case of Catch-22!

Of course, this will also happen if there is a programming error, or a CPU usage limit threshold met, or a timeout error, or a memory outage error or one of the other few dozen uncatchable errors which could abruptly terminate (kill) a backup process. However, it usually boils down to doing one of the seven steps mentioned in our backup troubleshooting document. And that's exactly why I wrote it.

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