Processing and Opening Errors
Closed this issue · 4 comments
PLEASE FILL OUT THE FOLLOWING. Bug reports with limited information or lacking an attached log file may get limited or delayed help.
Describe the bug
Errors processing books confirmed to be available today via Audible Plus Library
To Reproduce
- Go to and click on "Signal" Button for title
- See error
- Files seem to be showing up in Libation Books folder but Libation platform still showing Yellow Signal
- Restart of Libation now won't fully open and shows a new error
Expected behavior
Normal processing for titles confirmed to be currently available in Plus catalogue
Screenshots
Platform
Windows 11
Log Files
Thank you for your log. This appears to be related to Dropbox. The 1st error in your log is about Libation and Dropbox fighting over access to the same database file. The other errors are about the database being corrupted.
Since it's in Dropbox, they may have a way to roll back to a previous working version. If not, you'll need to delete the database file (Libation.db) and the search engine files (\SearchEngine folder) and do a new scan to re-build them.
Unfortunately I'm not sure how to prevent Dropbox, OneDrive, Google Drive, iCloud, etc from trying to aggressively fight over my files which change quickly during scans and downloads.
One option is to to move Libation stuff out of Dropbox.
Another option, and what I do personally, is pause Dropbox for an hour when I'm doing a scan or download. Then when I'm done it will automatically resume and pick up my changes.
That's helpful and clear. Thank you. I'll let you know here if I encounter any issues.
Thank you for your log. This appears to be related to Dropbox. The 1st error in your log is about Libation and Dropbox fighting over access to the same database file. The other errors are about the database being corrupted.
Since it's in Dropbox, they may have a way to roll back to a previous working version. If not, you'll need to delete the database file (
Libation.db) and the search engine files (\SearchEnginefolder) and do a new scan to re-build them.Unfortunately I'm not sure how to prevent Dropbox, OneDrive, Google Drive, iCloud, etc from trying to aggressively fight over my files which change quickly during scans and downloads.
One option is to to move Libation stuff out of Dropbox.
Another option, and what I do personally, is pause Dropbox for an hour when I'm doing a scan or download. Then when I'm done it will automatically resume and pick up my changes.
I don't know how feasible it would be, but an option would be to copy the database to the temp folder, process the changes there, and copy it back when done.
I did end up following your initial direction and that worked - though it (expectedly) did cause a longer recoup of my database. And I learned I need to pause the DB sync indefinitely (and manually restart the sync) rather than incrementally.