search

MommyHeather / AdvancedBackups

BSD 3-Clause "New" or "Revised" License
21 stars 5 forks source link

Bug report : Backup failure #68

Closed MuteTiefling closed 2 months ago

MuteTiefling commented 3 months ago

Describe the bug Since updating to 3.5, I've been getting this warning that the backup has failed. Logs appear to indicate it's getting stuck on something from Biomancy

To Reproduce

  1. Seemingly just allowing a backup to trigger with Biomancy installed.

Expected behavior Backup to complete as before

Screenshots image

Versioning (please complete the following information):

Additional context https://gist.github.com/MuteTiefling/cf1e4c6c660c242b27f8ebd1e88ace6d

MommyHeather commented 3 months ago

Hmm, and was 3.4 able to make the backup fine with Biomancy installed?

MommyHeather commented 3 months ago

Okay. I've been trying to reproduce this, to no avail.

With AB and Biomancy installed only, both scheduled backups and manual backups correctly hash the file and back it up.

Could I have a full modlist please? I'm also wondering why there's no visible stacktrace, as it's meant to print one out directly after reporting the error..

MuteTiefling commented 3 months ago

Hrm, alright. Wonder if something has gotten corrupt in my world then...

Forced a crash to get a full mod list for you: https://gist.github.com/MuteTiefling/a8af94ab98785a979f06124115582361

MommyHeather commented 3 months ago

I'd be surprised if corruption could do it... but perhaps, could you send over your AB config and the biomancy.spatial.db from the data directory?

MuteTiefling commented 3 months ago

Sure thing!

MuteTiefling commented 3 months ago

ab issue.zip

Take two!

MommyHeather commented 2 months ago

This is being fixed in multiple ways: