Support

We run many Joomla site (100+) all with similar software config.
Akeeba works very well on all of these sites, excellent software.
The latest site I have set up, Akeeba worked fine from the Joomla backend but the scheduled task (cron) fails with the error
"Couldn't write to the archive file; check the output directory permissions and make sure you have enough disk space available.[len=0 / 3] "
The back end backup and the cron task both use the default profile and store the backup in [DEFAULT_OUTPUT] and then transfer it to Amazon S3
The [DEFAULT_OUTPUT] -
administrator •
components •
com_akeeba •
backup
folder is set to 0755
What I don't understand is that both backups are writing to the same place, also we have unlimited space so that should not be an issue. Attached is a log file.

Let me know what extra information I can provide.
Thanks for any help.

Davide
Thanks for the reply. I have run it three time with the same results. It does start creating a file site-ndwg-org-uk.stackstaging.com-20181128-170658.j01 in the backup folder

Manage Backups says the three files were 3.8, 4.02, 4.83 Mb
I have attached the three log files

Running backup from Joomla still works okay

Davide
ok so I changed the archive part size to 3Mb
I then ran the cron task and the backup failed, log file attached.
I then ran a backup from Joomla > Akeeba and that ran fine.
yes very strange

Davide
what I find strange is that we have some 100+ site that were all set up by cloning a basic site (using Akeeba/kickstart)
This site is a new clone and hence should work the same as all of the ones before it.
I cannot see anything different in this installation from all the others. I have had very large site that back up with out issues.

I'll try what you suggest

I have tried removing the ramblers folder, no difference. See attached log file

I'll ask about CLI time limits, although there does not seem to be on other domains.