Support

Akeeba Backup for Joomla!

#27240 Joomla Backup fails

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by tampe125 on Tuesday, 14 March 2017 05:23 CDT

MikeWid
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: When my automated backup runs the first attempt fails after about 8 minutes, I then retry the same script which is successful, and only takes 3 minutes.
I am attaching a screenshot and log file which clearly shows the problem.
Please don't suspect my script.

tampe125
Akeeba Staff
Hello,

first of all, I'd need a log with more details, please change the log level to All info and debug.
However, I suspect the file you are creating is too large. Please set a part size of 20Mb and try again; you can find such option inside the Configuration page, in the section Archiver engine.
If it's still failing, please attach the new log with the new log level applied.

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!

MikeWid
Did you see the screenshot showing the specific error?
Here is a smaller screenshot.

tampe125
Akeeba Staff
Yes, but I need to see the full flow to understand the cause.
That's only the symptom, I need to find what is causing it. In order to do that, I need full details.
Please do as advised above.

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!

MikeWid
Here is the log from the failure last Friday.
The errors are not always the same.
Saturday and Sunday the backup worked without retries.

tampe125
Akeeba Staff
Inside the Configuration page, what's the value for the option Use database storage for temporary data? Can you please try to toggle it and try again?

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!

MikeWid
What is the point in that. This is an intermittent problem. Please pass this case on to a human.

nicholas
Akeeba Staff
Manager
You were talking to one of the two senior engineers of Akeeba Backup. Now you are talking to the MOST senior engineer, owner of the company, Joomla guru and well versed in server setup.

Davide was absolutely correct in asking you the question he did ask you. I will explain what lies behind it to demonstrate that there is ALWAYS a point. This is the first and last time I'll do that. When we do technical support we expect that you'll provide us with the necessary information we request in order to help you without having to explain why and without receiving derogatory remarks.

According to the log you posted:
DEBUG |170304 06:30:09|Saving Kettenrad instance frontend

DEBUG |170304 06:31:27|Kettenrad :: Attempting to load from database (frontend.id379) [frontend.id379]

DEBUG |170304 06:31:27| -- Stored Akeeba Factory (frontend.id379) [frontend.id379] not found - hard reset

DEBUG |170304 06:31:27| -- Loaded stored Akeeba Factory (frontend.id379)

We see two smoking guns here.

ONE: there is a one minute sixteen seconds gap between the two backup steps. That tells us that the server is probably overloaded or misbehaving. This makes us wonder why and what happened during that time.

TWO: the "hard reset" line tells us that the temporary data stored between steps has disappeared. The temporary data is either stored in files or in the database. We can reasonably wonder if the database is disconnecting / dying or if the host doing something silly, like intercepting and deleting our temporary data file (it wouldn't be the first time). Answering the question Davide posed will help us understand which of the two SERVER ISSUES is in play here.

One more thing. If I wanted to be strict about this ticket I would have closed it. It's outside the scope of our support. We do not provide support for server / hosting issues per our Terms of Service that you have agreed to when subscribing. You should be thanking Davide that he decided to help you, at least to the extent humanly possible.

Please stick to the technical questions you are asked. Any further snide remarks will result in ticket 27240 and all future tickets regarding the issue or the ticket 27240 itself to be closed without any further response. Consider this your final warning.

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!

MikeWid
Bear in mind that this is an intermittent problem.
The errors are different each occurrence.
My automated script runs on my local machine, at 06:30 am ( I have tried all different times)
It retries after errors until success, there can be 0, 1 or more retries.
I base success on downloading and parsing the logfile.
At your request, I have changed the values of "Use Database for storing Temporary Files" to 0.
The first manual attempt after that was successful.
I take your point about the server being suspect. My client can't do anything about that.
They are running the latest available versions of Joomla, Mijoshop etc.
I am going to all this trouble to help you to improve your product.

if "Use Database for storing Temporary Files" setting is critical then maybe you should change the default setting.

tampe125
Akeeba Staff
if "Use Database for storing Temporary Files" setting is critical then maybe you should change the default setting.
Each server has his own configuration. In your case the default settings didn't fit for you, other customers need it.
Please let me know if this solved your issue.

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!

MikeWid
This is the log from this mornings failed backup. The retry was successful.

tampe125
Akeeba Staff
The failure on the rename could be related to a filesystem issue. I can see you didn't set a part size; can you please set a part size of 10Mb and try again? You can find such option inside the Configuration page, in the Archiver engine section.

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!

MikeWid
How do I set a part size?

tampe125
Akeeba Staff
Inside Akeeba Backup Configuration page there is a section named Archiver engine. Clicking on Configure will show you the available details. In the field Part size for split archives set the value of 10.
You can find more info in this page of 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!

MikeWid
After changing part size to 10MB the first attempt this morning was successful.

tampe125
Akeeba Staff
Good, let me know if that fixed your issue for good.

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!

MikeWid
Just one failure since Friday.
See log.

tampe125
Akeeba Staff
INFO    |170311 06:30:27|Part size (bytes)  :2147352576

As I previously wrote:
The failure on the rename could be related to a filesystem issue. I can see you didn't set a part size; can you please set a part size of 10Mb and try again? You can find such option inside the Configuration page, in the Archiver engine section.

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!

MikeWid
Sorry, it was not saved, so I have now set part size, and it is now 10MB

tampe125
Akeeba Staff
Let me know if it fails.

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!

MikeWid
I think the backups are now succeeding.
When I check the log file in my script what text string would you recommend me to look for to judge success?
I am using "Post-processing has finished for all files", but this is not in the debug log (attached).

tampe125
Akeeba Staff
You should check if the string WARNING is inside the log file.
Otherwise you can setup a cron job to check if any backup failed, you can find more information here: https://www.akeebabackup.com/documentation/akeeba-backup-documentation/checking-for-failed-backups-automatically.html

Since your original issue is solved and this ticket is growing quite large, I'm going to close it.
If you have any other issue or question feel free to open a new one.

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 Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!