Support

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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:

Buongiorno,
da quando ho aggiornato all'ultima versione di Joomla il cronjob impostato su AWS non parte più, ne ho impostati due per due siti diversi sulla stessa macchina, uno funziona, l'altro non va e non capisco il motivo, ho anche aggiornato all'ultima versione di akeeba ma il problema non si é risolto.

Potreste aiutarmi?

Cordiamente
Piero

Davide is our Italian speaker, he will be on vacation this week.

If you look on the Manage Backups screen, does your CRON backup show there as a failed backup?

Does the backup work if you start it from the back end?

Hello!
Only work to mode manually: http://prntscr.com/fwoig3

this is the cron, to aurora work, to Anthroposnet not work: http://prntscr.com/fwojuf

What is the command of linux to run it from the command line, so as to see if the call is not starting.

Regards
Piero

The command to run the CRON job depends on which type of CRON job you are running, a command line backup or a front end backup. You can try to copy the command out of your CRON setup and use that on the command line. If that gives you an error, it would be something to work with.

You can see the correct command for your site under Scheduled Backups on the Akeeba Backup Control Panel. The different types of backups are on tabs on that screen.

it seem correct

50 02 * * * /usr/bin/php /var/www/html/********/cli/akeeba-backup.php

As the launch to line command?

Ok, I managed to run the file, the result is:


/usr/bin/php /var/www/html/*************/cli/akeeba-backup.php

Akeeba Backup CLI 5.4.0 (2017-05-18)
Copyright (c) 2006-2017 Akeeba Ltd / 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.
-------------------------------------------------------------------------------

You are using Joomla! 3.7.3 on PHP 7.0.16 (cli)

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

Current memory usage: 2.03 Mb

Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /var/www/html/**************
JPATH_ADMINISTRATOR : /var/www/html/****************/administrator

Last Tick : 2017-07-17 16:24:01 GMT+0200 (CEST)
Domain : init
Step :
Substep :
Memory used : 5.1 Mb
Warnings : no warnings issued (good)

An error has occurred:
Failed configuration check Q001: Output directory unwritable. Please refer to https://www.akeebabackup.com/documentation/warnings/q001.html for more information and troubleshooting instructions.

Peak memory usage: 5.16 Mb

risolve! the problem is folder administrator/components/com_akeeba/backup whit permits 775, I change 777 how work!

is correct?

Correct, that is necessary on some servers. You should have an .htaccess file in that folder that protects the files from outside access. That is important since we can't use file permissions for security.

Should I do something about .htaccess file

Please make sure it is there. Note that any file that begins with . is a hidden file.

It the file is there, I have to write some rules inside?

No, the rules to protect the files in that directory are already there. That is what the .htaccess does. You are fine.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.