Support

Akeeba Solo

#35253 Akeeba Solo always fails integrity check

Posted in ‘Akeeba Solo (standalone)’
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

PHP version
n/a
Akeeba Solo version
n/a

carcam

Good morning Akeeba team!!

I am puzzled with an issue I have with one of my current backups.

Backups are correctly taken if I launch them from Akeeba Solo web interface, but when started through a cronjob, the backups are not sent to my remote storage.

After checking the logs I see that the problem is the Archive integrity check, which always fails when in the cronjob (see attached log).

I have 2 more other instances for other 2 similar sites of Akeeba Solo in the same server and all run through a cronjob (at different times with around 60 minutes between them) and quite similar in configuration and in the sites structure (quantity of image files and database size is probably the only difference).

I have tried changing the part size of the jpa with no results.

Is there a way to know why is the integrity check failing?

Thank you very much for your assistance!!

tampe125
Akeeba Staff

Hello,

the integrity test will try to extract your archive without writing any file to disk. Did you try to download the archive and restore it locally? Is it truly corrupted or not?

From there we can start working on the root 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!

carcam

Trying to restore in a different server ends up with an error when the restoration is almost complete. Does kickstart have any kind of log that I can check?

tampe125
Akeeba Staff

First of all, update the Kickstart version you're using, you're more than 2 major versions behind :)

Then open the kickstart.php file and remove the comment on KS_DEBUG, then run the extraction again. A new debug file will be produced, zip it and attach it here. It should tell us where it is failing.

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!

carcam

Hi Davide,

Wow!! Nice redesign!! I have checked with latest pro release and attached you may find the debug log.

Also taking a peek showed me a couple of file exclusions I can do to reduce the backup file.

In any case I'm not able to find the specific problem with my current knowledge so any input will be appreciated.

Best!!

tampe125
Akeeba Staff

It seems that the corrupted file is this one: /autoupgrade/backup/auto-backupfiles_V1.7.6.7_20201124-185029-2e9a45db.zip

If you look at the debug file, it seems that the file is spanning several archives since it's very large. I suspect such file changed in size while taking the backup, this is why you ended up with a corrupted archive.

There's no point in backing up other backups, I'd suggest you to exclude such folder and run another backup, your problems should be solved.

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!

carcam

Hi Davide,

that is great news!! I actually noticed that file in the log too and I removed it from the serve as I totally agree with your conclussion. So that means that tomorrow my backup will go seamlessly and it will also be  half size that it is now. All good news!!!

I will close this ticket tomorrow if everything goes well.

Best!!

 

tampe125
Akeeba Staff

Awesome! I'm glad that fixed 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!

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!