Akeeba Backup for Joomla!

Tuesday, 31 August 2010 06:45 CDT

user12466

We've got a cron job that always results in 500 error.
It seems to stop during the DB backup (hasnt reached file backup yet).
Any recommendations on waht "Fine Tune" settings to use to resolve?

Tuesday, 31 August 2010 09:09 CDT

dlb

Please zip and post your backup log file. That may shed some additional light on the problem.

Dale L. Brackin
Support Specialist

English: 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)

Wednesday, 01 September 2010 04:04 CDT

user12466

Attached. Thank you.

##text##

Wednesday, 01 September 2010 08:44 CDT

dlb

It is actually timing out while writing some temporary data from the database dump. It may be just a matter of adjusting the timing numbers, but I have a feeling that it isn't going to be that easy. I want Nicholas to take a look at the log.

Dale L. Brackin
Support Specialist

English: 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)

Thursday, 02 September 2010 00:03 CDT

nicholas

No, it's very simple. Click the "Configure..." button next to the Database Dump Engine. In the pane which opens below set the number of queries per batch to 100 (drag the slider leftwards until the reading is "100 queries"), save the configuration and retry your 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!

Monday, 13 September 2010 09:23 CDT

user12466

Nicholas, we've done as instructed above but are getting the same error/results.

Monday, 13 September 2010 12:08 CDT

nicholas

I reread the thread and I just realized that you are talking about a CRON job, which makes things a bit different. I can see that the backup is being killed 60 seconds down the process, because you are using the wrong PHP executable file. According to the log you are using the PHP CGI script, designed to run PHP files over the web, which has a time limit of 60 seconds. You have to ask your host to tell you the full path to the PHP CLI (Command Line Interface) binary which is designed for running lengthy processes and doesn't have a time limit. Detailed information on setting up the CRON job once you have this information can be found in the documentation.

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!

Thursday, 07 October 2010 04:45 CDT

user12466

Nicholas, the host replied saying:

"The php executable binary is located in /usr/bin/php"

Thursday, 07 October 2010 23:42 CDT

nicholas

See, that's what I'm talking about. Your hosts pointed you to the location of the PHP CGI binary. The PHP CGI (Common Gateway Interface) binary is meant to be used by the web server to serve pages. As a result, it is bound by the time limitations of its php.ini file. We want your host to tell you the location of the PHP CLI (Command Line Interface) which is not bound by time limits. Please escalate your support ticket with your host and ask them for the location of the PHP CLI binary. The first line of support are usually not educated enough to figure it out. Escalating your support ticket will most likely land it to the hands of someone who can tell the difference and let you know of the location of the correct binary.

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!

Thursday, 11 November 2010 06:07 CST

user12466

Host keeps replying saying its

"The full path to the PHP CLI binary is /usr/bin/php"

Are there any other options to get it working aside from switching hosts?

Friday, 12 November 2010 03:26 CST

nicholas

The support guys at your host are ridiculous. You should try escalating your support request demanding the full path to the PHP CLI binary. Explain them that the CLI binary is the one which is designed to run command-line applications and has no time limit. What they are giving you is the CGI binary which is not what we want.

The other two alternatives are:
1. Guesswork. If your host is using cPanel, then there's a 99% chance that the path to the PHP CLI binary is usr/bin/php5-cli
2. If all else fails, switch hosts :(

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