Support

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:
i have recently upgraded my site from 2.5 to J3.3.6 All well. Installed latest versions of Akeeba BU and Admintools. No problem. i have two profiles for backups one with upload to S3 and one without. The one WITH upload to S3 runs daily in a cron-job (native) and has worked like clockwork since it has been installed. In the default profile I have not activated upload to S3.

The following now started to happen:

Run BU from back-end using def profile : no problem
Run BU from cron using S3 profile : BU completes but file does not get uploaded to S3

First I thought it had to do with maybe renewing keys for AWS after upgrade so I did that. BU from CL still not gets uploaded. I cannot really find errors in the log files and get no error messages.

So I added the upload to S3 to the def profile: BU completes AND uploads to S3 fine.

Then I selected the S3 profile and started BU from back-end: BU runs fine AND uploads to S3.

So all looks fine and seems to be working the only thing that does not happen is the upload to S3 when the job is triggered from the Command Line. I do get the message with the log of the BU job being triggered AND the BU file is available in the backend but the file does not get uploaded to S3 ....

No clue anymore, hope you can help

JdK

Siteground imposes a time limit on CRON jobs, the default is 150 seconds. When the limit is reached, they kill the CRON job, assuming that it is a runaway.

In the log you posted the CLI backup stops at exactly four minutes. My guess is that you have run into this problem before and Siteground increased the CRON timeout, but your site has grown enough that the four minute limit is now exceeded. It works from the back end because this particular limit only applies to CRON jobs. Please talk to Siteground about increasing the time limit for the CRON job.

Hi Dale, Thanks for this insight. Makes sense :)
I will clean up some leftovers from the site migration and try again when site and database are not bloated any more. If problem persists I will contact SG.
Thx, Jdk

That sounds like a good plan. My understanding is that Siteground is pretty reasonable about changing the limit for legitimate CRON jobs that are being killed.