Support

Hi Support,

We are getting the following message, whereas we have unlimited space on hosting and other Akeeba Solo backups are working fine except one. i m attaching the screenshot and the log file for review. Please do let us know the solution for the issue.

------ BEGIN OF ALICE RAW OUTPUT -----
Timeout while backing up
There is already an issue with the backup engine saving its state. Please fix it before continuing.

Fatal errors
The following fatal error happened while taking a backup. Please review and fix it before continuing:
Couldn't write to the archive file; check the output directory permissions and make sure you have enough disk space available.[len=0 / 4]

------ END OF ALICE RAW OUTPUT -----

The ALICE output really doesn't help in diagnosing the problem. Please zip and attach your backup log.

Here is the backup log with other supporting files

The files did not come through. You will probably need to zip them to get them to post. If you still have trouble, just throw them up on a file service like Dropbox, etc. and post the link, I'll go get them.

Hi Support,

I think they are not attaching over here so please download them from https://drive.google.com/open?id=0B72F5zwKpwlwSnZVRDdrdG1uZ3M

We can eliminate the part size being too large because this is the third part. If it was part size, it would have failed with the first part. And you appear to have enough disk space. These are the two most common reasons for the error.

Please change your archive type to jpa and try your backup again. It is possible we're hitting a CPU limit and the jpa format is more processor friendly.

Hi,

I have tried to use JPA and Part size for split archives to 1024MB but the backup failed. Please check the log at https://drive.google.com/open?id=0B72F5zwKpwlwTFFheHdlYVZJbTg and advise..

The part size is usually a problem when uploading the archive to cloud storage. This backup is failing before that, while archiving files. Let's try to slow the backup down, so we're using the CPU cycles over a longer period of time. Please go to your Akeeba Backup Configuration page and try setting:

Minimum execution time: 1 seconds
Maximum execution time: 20 second
Execution time bias: 75%

If is still does not complete, try:

Minimum execution time: 5 seconds
Maximum execution time: 1 second
Execution time bias: 50%

Yes the minimum is larger than the maximum, that's not a typo.

It is failed in both way. Please the log files at https://drive.google.com/file/d/0B72F5zwKpwlwT3RGWFl6OE9ySzg/view?usp=sharing
https://drive.google.com/file/d/0B72F5zwKpwlwNHg1Y3F3Y2hmMjA/view?usp=sharing

I can provide you the site details for further debugging if required.

My apologies, my reply was for another ticket.

Most hosts have both disk space limits and inode limits. The inode limit is a limit on the total number of files and folders on the site. Can you please check if you are near or have exceeded the inode limit for your account? My host shows this information on the cPanel, if yours does not, you may need to ask them.