Akeeba Backup for Joomla!

Friday, 03 November 2017 05:01 CDT

borox

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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:

Hi,

I use a CRON to backup on S3, with one the backup profile I have a very large log file ( 2GB!), I manage to get the begining, I think that it's full of these lines:

DEBUG |171102 02:00:06|Akeeba\Engine\Core\Domain\Finalization::_run() Running add-on method test_extract
DEBUG |171102 02:00:06|Akeeba\Engine\Core\Domain\Finalization::_run() Running add-on method test_extract
DEBUG |171102 02:00:06|Akeeba\Engine\Core\Domain\Finalization::_run() Running add-on method test_extract
DEBUG |171102 02:00:06|Akeeba\Engine\Core\Domain\Finalization::_run() Running add-on method test_extract
DEBUG |171102 02:00:06|Akeeba\Engine\Core\Domain\Finalization::_run() Running add-on method test_extract
DEBUG |171102 02:00:06|Akeeba\Engine\Core\Domain\Finalization::_run() Running add-on method test_extract

It doesn't seem to happen all the time, I just tried to force the CRON and there was no problem. But it already happened twice.

Thanks

Nicolas

Friday, 03 November 2017 10:46 CDT

tampe125

Hello,

I suspect the host is removing some temporary files used to test the extraction, so it gets stuck in a loop.
Can you please check the option Use database storage for temporary data inside the configuration page and try again?
Is still stuck?

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!

Sunday, 26 November 2017 04:12 CST

borox

Hi,

Sorry, I switched to something else, but the problem just come again. I checked the option 'Use database storage for temporary data '.
But how can I stop the actual log who is growing?

Thanks.

Nicolas

Sunday, 26 November 2017 04:13 CST

borox

Sunday, 26 November 2017 12:51 CST

borox

Hi,

Fortunately the job stopped itself ( after a 10Go file), but for the next time, is there a way to stop the job to avoid this growing files?

Thanks.

BR

Nicolas

Monday, 27 November 2017 02:40 CST

tampe125

It seems that the problem was caused during the integrity tests after the backup is being taken.
Since we're performing an in-memory restoration, the process uses a lot of resources. I suspect your host is blocking or limiting the amount of resources you can use, that's why it takes so long, causing the error log to grow very large.
In such cases, the best solution is to remove the flag from the option Integrity check inside the Configuration page.

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, 27 November 2017 03:00 CST

borox

Hi,

Thanks for your answer. I will consider stopping testing the integrity of the backup.

Once we are in this kind of dead loop, is there a way to end it?

Thanks
BR

Nicolas

Monday, 27 November 2017 03:05 CST

borox

Does it mean that using the option 'Use database storage for temporary data' won't change anything ( if the problem )? would't we have a growing table instead of a growing file in that case?

Thanks.

BR

Nicolas

Monday, 27 November 2017 03:11 CST

tampe125

Once we are in this kind of dead loop, is there a way to end it?

That's something only your host can do, since he will have to kill the process. Once a PHP request is started (not only our backup process, but ANY page) the server will continue its work until it's done, even if you close your browser.

Does it mean that using the option 'Use database storage for temporary data' won't change anything ( if the problem )? would't we have a growing table instead of a growing file in that case?

That was a workaround for hosting deleting Akeeba Backup temporary files. Instead of writing data on the file system, we use a temporary table: data is always replaced and updated, not added. So you won't have any huge tables.

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, 27 November 2017 03:17 CST

borox

Thanks, that's clear.

What information do we have to give to the host to kill the akeeba process?

Thanks

BR

Nicolas

Monday, 27 November 2017 03:22 CST

tampe125

Telling your site name and the CLI file that you used to trigger the backup should be enough. They'll be able to search inside the active processes and kill it.

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, 27 November 2017 03:25 CST

borox

Thanks Davide

Have a good day.

BR

Nicolas

Support