Support

Akeeba Backup for Joomla!

#9023 CRON automation

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 Sunday, 25 September 2011 11:58 CDT

user44947
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?)? Yes, on automated cron backup
Joomla! version: 1.6
PHP version: (unknown)
MySQL version: (unknown)
Host: rochen
Akeeba Backup version: most recent pro

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:

I am trying to automate daily backups using the CRON backup and keep getting this email (follows) but don't get a backup completed email, unlike when I do a backup from the akeeba component directly. It seems like something is going wrong with the automation, any help is greatly appreciated! Thanks!

"Akeeba Backup CLI 3.3.3 (2011-08-14)
Copyright (C) 2010-2011 Nicholas K. Dionysopoulos
-------------------------------------------------------------------------------
Akeeba Backup is Free Software, distributed under the terms of the GNU General
Public License version 3 or, at your option, any later version.
This program comes with ABSOLUTELY NO WARRANTY as per sections 15 & 16 of the
license. See http://www.gnu.org/licenses/gpl-3.0.html for details.
-------------------------------------------------------------------------------

Starting a new backup with the following parameters:
Profile ID 1
Description "Command-line backup"

Current memory usage: 727.08 Kb

Unsetting time limit restrictions."




nicholas
Akeeba Staff
Manager
The log file you provided is from the back-end backup, not the Command Line backup.

Anyway, considering the cut-off output of the script I think I know what the problem is. You seem to be using the PHP CGI binary instead of the PHP CLI binary. Moreover, your copy of PHP is running under Safe Mode. This setup is incompatible with backup.php and altbackup.php

Please ask your host which is the full path to the PHP CLI (Command Line Interface) and use it in your CRON command line. Please note that the CGI (Common Gateway Interface) binary you are using is designed to run web accessible scripts, whereas the CLI binary we want is designed to run command-line applications and lifts several restrictions (like the time limit).

If all of this is over your head or you can get your host to figure out where the PHP CLI binary is located, please use the front-end backup feature with wget or curl in your CRON job. It works equally well and it is the easiest to setup.

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!

user17459
Hi Nicholas,

I get this email when i run the cron job, althogh the backup doesn't run, any ideas?;

X-Powered-By: PHP/5.2.17
Content-type: text/html

Akeeba Backup CLI 3.3.4 (2011-09-12)
Copyright (C) 2010-2011 Nicholas K. Dionysopoulos
-------------------------------------------------------------------------------
Akeeba Backup is Free Software, distributed under the terms of the GNU General Public License version 3 or, at your option, any later version.
This program comes with ABSOLUTELY NO WARRANTY as per sections 15 & 16 of the license. See http://www.gnu.org/licenses/gpl-3.0.html for details.
-------------------------------------------------------------------------------

Starting a new backup with the following parameters:
Profile ID 1
Description "Command-line backup"

Current memory usage: 127.06 Kb

Unsetting time limit restrictions.

nicholas
Akeeba Staff
Manager
Hi Rob,

This means that the CRON job did start, but it never made it as far as to loading the backup engine. This usually indicates a strange path setup on your server. In those cases, you can use the classic front-end backup feature with wget or curl in your CRON job. Please read the relevant documentation section at https://www.akeebabackup.com/documentation/akeeba-backup-documentation/automating-your-backup.html#frontend-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!

user17459
Hi Nicholas,

Do you know anyone using Hostgator and what path they use for the cron job, I'd much prefer not to use the front end backup.

Thanks
Rob

nicholas
Akeeba Staff
Manager
Hm... Is it possible to ask your host for the PHP error log for the time of the backup? If I get to see the exact error message which occurred when the CRON job failed, I can tell you exactly what needs to be done.

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!

user17459
Hi,

I went with the front end backup.

Thanks

nicholas
Akeeba Staff
Manager
You're welcome!

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!