Closed anantone closed 4 weeks ago
Yeah this is a bug in the current version that occurs when the ingest script is interrupted prior to completing an ingest i.e. if you restart the container during ect.
It's already fixed for the next version, for now just run rm /tmp/new-book-processor.lock
and you should be good to go again
Awesome, it works! Thank you for the quick answer.
When adding a new book to the "ingest" folder, this message appears:
What happens instead is the file remains in the ingest folder, and is not added to the library.
I'm running the latest Docker image on Ubuntu 24.04 with the compose file below. Permissions are coherent throughout.
I've tried restarting the container with an empty ingest folder, then adding the file; restarting the container with the file already in the ingest folder... Nothing doing. Not able to import books through ingest folder.