You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw this issue came up earlier in #165 but the fix listed there doesn't work for me so I'm opening this as a new issue.
CWA-Check Results
root@a7647cb41e46:/# cwa-check
====== Calibre-Web Automated -- Status of Monitoring Services ======
s6-rc: fatal: unable to take locks: Resource busy
- cwa-ingest-service is not running
s6-rc: fatal: unable to take locks: Resource busy
- metadata-change-detector is not running
Calibre-Web-Automated was not installed successfully, please check the logs for more information.
Logs upon starting container:
[cwa-auto-library] Library location successfully set to: /calibre-library
========== STARTING CWA-INGEST SERVICE ==========
========== STARTING METADATA CHANGE DETECTOR ===========
[metadata-change-detector]: Watching folder: /app/calibre-web-automated/metadata_change_logs
[cwa-ingest-service]: Watching folder: /cwa-book-ingest
Setting up watches.
Watches established.
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
I tried running rm -r /tmp/* in the containers cli as recommended in #165, but get the following error: rm: cannot remove '/tmp/*': No such file or directory
Following up to say I've updated to 3.0.1 and migrated my library from an NFS mount to a local mount on the machine and am still getting the same response when I run cwa-check. My logs are below. Loving this tool, thank you!
I saw this issue came up earlier in #165 but the fix listed there doesn't work for me so I'm opening this as a new issue.
CWA-Check Results
Logs upon starting container:
I tried running
rm -r /tmp/*
in the containers cli as recommended in #165, but get the following error:rm: cannot remove '/tmp/*': No such file or directory
Originally posted by @malewpro in #165 (comment)
Configuration:
I should also note that I've tested the "latest" build and the "dev" build and see the same issue in both instances.
The text was updated successfully, but these errors were encountered: