Support

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, Native and Alt CRON docs
Joomla! version: 2.5.7
PHP version: 5.3.13
MySQL version: 5.5.27
Host: ICDSoft (www.icdsoft.com)
Akeeba Backup version: 3.6.5 Professional

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:

I am getting this error when running the NATIVE CRON:

AEAbstractDump :: Database Error: Could not connect to MySQL

The script starts to run, but stops there. I looked through the posts and tried--

1) setting max execution time to 7 (my host is at 120)
2) using JPA format and setting"Part size for split archives" to 2.00
3) checking for extra database definitions under "Multiple Databases Definitions", and there are none there.

I have also tried using the ALT CRON, but got these errors:

ERROR:

	This script could not detect your live site's URL. Please visit Akeeba

	Backup's Control Panel page at least once before running this script, so

	that this information can be stored for use by this script.

ERROR:

	Your Akeeba Backup installation's front-end backup feature is currently

	disabled. Please log in to your site's back-end as a Super Administra-

	tor, go to Akeeba Backup's Control Panel, click on the Parameters icon

	in the top right corner and enable the front-end backup feature. Do not

	forget to also set a Secret Word!

BACKUP ABORTED DUE TO CONFIGURATION ERRORS

I have used the backup control panel already and the front-end backup feature *is* enabled, so I'm not sure what that doesn't work.

Any assistance would be greatly appreciated. Thanks!! Hope you enjoy the Joomla Day conference!

Hey, thanks for the reply!

I'm getting the same error(s) with the dev release. The logs are attached.

Also for the ALT script, the front-end feature *is* enabled and I do have a secret word setup, but I am still getting that error.

Also I found the CLI log file in the default Akeeba backup directory, instead of the directory that I setup in the config (not sure if that makes a difference).

Thanks again.

Ok, I can ask host about this.

I am using the scripts in the cli directory (I just purchased AKP so I don't have any older scripts). I was just saying that the log file that was created was created in the Akeeba default directory for some reason even though I have a different directory specifie in the config.

If I can't get this host to change their cli config, do you have any recommendations for hosts that work with this software?

Thanks!

The akeeba cli log is created in the default directory, along with the .jpa files that failed in the cron. I just assumed that was due to the cron failure, as running a backup manually works perfectly.

Thanks for the recommendations!

OK, I have more information for you!

My host does have mysql connections through cli enabled. The problem was actually happening because I had moved my configuration.php file outside of the web root. I was using the defines.php override method, outlined here:

http://docs.joomla.org/Moving_sensitive_files_outside_the_web_root

Once I moved my configuration.php file back into the root directory and canceled the override, the cron proceeded without an error and created my backup file.

Have you heard of this before and if so, is there a way I can use Akeeba Backup while still having the config file outside of the root? I would like to do that for security.

Ha! That blog post just pwned my life!

Ok, man. All is good then. Thanks a lot for helping during your vacation.