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
Joomla! version: 2.5.8
PHP version: 5.3.16
MySQL version: 5.5.27
Host: Media Temple
Akeeba Backup version:3.6.9
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: Frontend backup fails.

I have just started to use the cron job for backing up my sites and then moving the backups to Amazon S3.  It works fine for 3 of the sites, but for some reason, it is failing on one site.  Backing up the site from the backend works fine.

One very weird thing is that the Component Paramters keep being reset to the default (Enable front-end and remote backup, Secret Word, etc.).  I noticed this yesterday and not matter how often I set the parameters, they would be reset when I opened the parameter dialog.  I even manually set the JSON string in the database with the correct values, but when I brought the dialog up, the parameters would be reset!

So I ended up just setting the parameters and leaving them.  Accoridng to the log, the cron job ran overnight but the control panel indicates that the backup failed.

I've attached the frontend log, I can also send the backend log if that would help.

Ok. I just uninstalled and installed 3.6.10.  Now when I try to save the components parameters, I get the message: Could not save data. Error: The database row is empty.

On the CRON daemon running out of time, I was able to run the job successfully via the cron in my initial testing.  I've now excluded the .git directory as well as some database tables that are not needed so hopefully that will reduce the time it takes to backup the site.

One of the main critical tables is over 1gig.  I'm running a backup now, and it is taking much longer than I expected.  I'll post the log file when/if it completes!

yes, there is the one record in the ak_profiles_table.

I went through the troubleshooting steps and was able to make some progress. After saving the result of the configuration, the 'Could not save data...' message does not appear when saving the component parameters.  Unfortunately, the parameters are still not saved???

I just got back from lunch and noticed that the last backup attempt from the backend failed with:

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

I've attached the log file from that run.

One thing that may be causing the problem is that we at 90% of our alotted disk space on our server.  That is one of the reasons we are trying to move as much stuff as possible to S3.