Support

Akeeba Backup for Joomla!

#9121 Ajax 500 error during backup on 1and1.co.uk

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 Monday, 31 October 2011 16:17 CDT

Saturday, 29 October 2011 06:58 CDT

user48995
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the forum before posting? Yes
Have I read the documentation before posting (which pages?)? User Guide
Joomla! version: 1.5.23
PHP version: 5.2.17
MySQL version: 5.0.91-log
Host: 1and1.co.uk Linux Business Package
Akeeba Backup version: Akeeba Backup 3.3.4 (2011-09-12)

EXTREMELY IMPORTANT: Please attach your Akeeba Backup log file in order for us to help you with any backup or restoration issue.

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

Referred to Troubleshooter.

http://www.berksfhs.org.uk/cms/administrator/index.php?option=com_akeeba&view=browser&format=raw&processfolder=1&folder=%5BSITEROOT%5D
Note - cms folder!

There is a second Joomla website www.berksfhs.org.uk/shop

This also fails on test site (on 1and1) but backup completes OK.
Just disabling plugins but still failed.

Setpoint seemed to work on sh404sef upgrade.

Tried settings for one.com in abbackup.html still no joy.

Joomlapack 2.4.1 used to work but now doesn't work on shop web site (Ajax error)

This browser is Firefox 7 but I've tried IE8 too.

Hope you can help direct me.

Saturday, 29 October 2011 07:35 CDT

dlb
You are not very far into the backup process, it is still dumping the database. One thing that can cause a 500 error there is a file size limit from your host. If you have such a limit, you will need to split your backup archive into parts. The part size is set on the Configuration page, press the Configure button on the Archive Engine line.


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)

Saturday, 29 October 2011 08:00 CDT

nicholas
Another thing, which I am not sure if it applies to 1and1, is the MySQL query limit. Some hosts limit the number of MySQL queries you can execute per hour. You can check if there is such a limitation on your host by asking them.

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!

Sunday, 30 October 2011 19:12 CDT

user48995
I can perform a backup - but only by excluding the akb_content table! I ran the configuration wizard again and performed another backup at a better speed again without akb_content.

I have bulk loaded some articles into the jos_content table so I may have done something wrong here.

I can dump the jos_content table into SQL using PHPmyadmin - so I have a complete backup (or do I?)

Will report back if I find the problem. - Chad

Sunday, 30 October 2011 19:16 CDT

user48995
Just to note: in the last post was translated into akb_

Monday, 31 October 2011 02:50 CDT

nicholas
There is a workaround to that. Go to Akeeba Backup's Configuration page and find the Database Dump Engine setting. Click the Configure button next to it. Set "Number of rows per batch" to a smaller number. Using 100 or even 20 should do the trick, but the backup will be slightly lower.

If you're wondering why is that, it's a low PHP memory limit. When backing up the database, Akeeba Backup loads a batch of rows in memory. By default that is 1000 rows. Then we dump those records to the SQL dump file. We do that for performance reasons (it's much faster than querying each row individually). However, if you have large records, e.g. very large articles, this requires a lot of RAM. If the PHP memory limit is below 64 Mb, it can cause a memory outage which manifests itself as an Internal Server Error 500, displayed during backup as "Ajax Error 500".

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!

Monday, 31 October 2011 12:00 CDT

user48995
Yes, that makes a great deal of sense - we do have many large articles. The test system does not have all the content, just the same extensions, etc.

I will try this later.

Many thanks for the service and the product!
Chad

Monday, 31 October 2011 16:17 CDT

nicholas
You're welcome! Let me know how it goes :)

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!