Akeeba Backup for Joomla!

Saturday, 07 April 2018 16:11 CDT

arlattimor

Have recently purchased Akeeba Backup Professional 6.0.1. My hosting provider is 50webs.com, I have followed the instructions on how to create a Cron job using the Akeeba Script. Bit I get no indications that the script has ran during the scheduled time for the backup. Nor can I find any backup files. when 50webs support runs the Akeeba Script manually thru SSH, they tell me that the script did run. But when I chack the backups in Akeeba, its says the the Command Line Backup has failed.

Any assistance would be greatly appreciated.

Edited by arlattimor on 2018-04-07 16:13 CDT

Saturday, 07 April 2018 16:14 CDT

arlattimor

Monday, 09 April 2018 02:07 CDT

tampe125

Hello,

looking at your backup log file, the process is killed after two minutes sharp.
This means that the host is applying some kind of timeout on CLI scripts. Please get in touch with them and ask them if they can raise such timeout for your site.
If that's not possible, you'll have to run backups using an external service like WebCron.org

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 09 April 2018 04:36 CDT

arlattimor

Just how long should the timeout be increased to? When I run a manually backup thru Akeeba it takes about 7.5 minutes to tun.

Monday, 09 April 2018 04:52 CDT

arlattimor

Also, here is the latest log from the backup that tried to run on Sunday evening at 9:15 p.m.. I use the Alternative Command-Line Cron to see if that would make a difference and that also failed.

Monday, 09 April 2018 04:53 CDT

arlattimor

Monday, 09 April 2018 05:13 CDT

tampe125

Just how long should the timeout be increased to? When I run a manually backup thru Akeeba it takes about 7.5 minutes to tun.

Try to ask for 5 minutes, it should be enough for a CLI backup.

Also, here is the latest log from the backup that tried to run on Sunday evening at 9:15 p.m.. I use the Alternative Command-Line Cron to see if that would make a difference and that also failed.

That's unrelated. Using the alternative way is for another kind of issues.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 09 April 2018 06:38 CDT

arlattimor

Well that is a no go with my hosting provider they are not willing to do anything with changing any server settings. So what would be my other options becuase this is what they are telling me.

All our servers are set on UTC timezone and you need to adjust your cron run time according to this to suit your local time. Server time can not be changed.
Timeout on cronjobs can not be changed as well and you will either need to optimize your script to be processed on a shorter period

Edited by arlattimor on 2018-04-09 06:48 CDT

Monday, 09 April 2018 07:26 CDT

tampe125

In that case you have to rely on an external service like WebCron.org to trigger your frontend backups.
The backup happens during page load, so you shouldn't hit any timeout. For further info please take a look at the documentation

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support