Akeeba Backup for Joomla!

Friday, 03 June 2022 04:42 CDT

beeweebee

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 10MiB, please upload it on your server and post a link to it.

Friday, 03 June 2022 04:44 CDT

beeweebee

I haven't finished the ticket and submitted by error.

The Akeeba version is : Akeeba Backup Professional 8.1.5

Please see the log of the CRON I got attached and let me know what's wrong.

Thanks.

Friday, 03 June 2022 06:18 CDT

nicholas

You have sent me a zero byte file. It contains nothing and tells me nothing.

Please do try to upgrade Akeeba Backup — we released a new version earlier today — and retry reproducing your issue. If the backup does not start at all and generates no entry in the Manage Backups page the problem is how you've set up your CRON job. Beyond what you can already read in the documentation I've written myself all you can do is ask your host as to why the CRON job didn't execute.

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, 11 July 2022 03:50 CDT

beeweebee

Hello there,

Sorry for the late reply. I've upgraded Akeeba to latest version couple weeks ago (it was 8.1.7). So the latest CRON ran on that version.

I've downloaded the latest CRON error log from last Thursday. Please find it attach (this time it's not empty).

Error is still the same:

/bin/sh: /var/www/clients/client109/web392/web/cli/akeeba-backup.php: Permission denied

I think the CRON is properly set up to run otherwise I wouldn't get this message. So from your experience, my question is still the same: why could create this "Permission denied" issue?

Thanks for your help,

Bruno

Monday, 11 July 2022 03:59 CDT

nicholas

This message does not come from Akeeba Backup. It comes from your host and it means that their CRON server cannot access the file which needs to run for the backup to execute. As you can understand, at this point our code does not run (since your host cannot load it), therefore this is not an "issue that we have created", it's a misconfiguration on your hosting account.

Please contact your host, show them this error message and they will help you set up the CRON job correctly.

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