[Synology NAS] CWA not currently working on Synology Devices #55
Comments
|
Could you please Also make sure you're using the new docker compose: |
|
I have the same problem! Had it with the RC too, not with 1.2.2 but then the permissions were the problem afterwards (I'm very happy that's fixed!!) I checked My root folder within the container, its empty... |
It seems the only issue I had with my docker compose setup was the missing drwx------ 1 root root 4096 Aug 30 09:38 ./
drwxr-xr-x 1 root root 4096 Aug 30 09:38 ../
-rw-r--r-- 1 root root 3470 Aug 29 17:49 .bashrc
drwxr-xr-x 2 root root 4096 Aug 30 09:38 .config/
-rw-r--r-- 1 root root 161 Jul 9 2019 .profileAfter making this change, everything seems to be functioning properly again - books placed in the ingest folder are now added to the library and appear in the web UI. Looking back at the v2.0.0 announcement, I realized that, at least for me, it would have been helpful to more clearly emphasize the two breaking changes for existing setups: the change in the library path from Great project! |
|
Did a system prune (incl volumes) and installed everything from scratch just to rule out errors... still the same problem; the book seems digested fine but doesn't show up in the web ui.
|
Are you sure |
|
Yup, this is the full compose file: |
|
Maybe it's relevant info that I'm on a Synology DS220+? The PGID/PUID is from a seperate docker user that has read/write rights to all the relevant folders. |
Ah that does make a difference, if you use the default PUID 1000 & PGID 100 does it also not work? |
|
1000:100 doesn't seem to have access to the library folder! I never use those PGID/PUID, I don't even know what account they link to. I'll try next with my regular admin account numbers... |
|
The PGID/PUID of my regular admin account gives even stranger logs... I removed a lot of clutter after this log part; its a never ending repeating error log with those three headings At this point, the PGID/PUID i normaly use for docker containers seems to give the most functioning option by far. |
|
Very odd, do try 1000:100 in the docker compose though if you haven't already, they're pretty much only used to set the permissions to abc:abc for the directories and files that CWA needs to function, including the library during init. |
|
I've tried almost all options I could think of, but the PGID/PUID i always use for docker containers (a dedicated docker user with the right permissions) is the only one that works as it should! except for the digesting of new files via watch folder, but other than that it's perfect! For now I'll just accept this part not functioning. I can upload files via the UI anyway. Only downside is manualy scraping metadata afterwards, but that's not a big problem for me. Anyway, thanks a lot for creating this fork! it gives me so much more use out of CW |
Hey @iroQuai , so someone in the Discord was facing similar issues to you with a NAS based system. He found a fix where if the temp folder used internally for imported processed files is mounted in the same system as the ingest folder, everything works as intended. The temp folder to mount is at If you can also confirm this works, I can start work on a fix where the temp folder is no longer needed for ingest and it should improve compatibility across the board. |
|
I added I tried to use the ingest folder again. Same result, sadly. But a new error message, maybe it gives a lead? These are the last lines of the terminal logs: |
|
I just wanted to add on here, new user as of tonight. I'm using a synology NAS and when I drop in an epub it just disappears with nothing being loaded into the program. |
crocodilestick
changed the title
crocodilestick
changed the title
|
@techdixie @@iroQuai But that would mean that even though the Calibre docker mod is in both of your docker composes, somehow the Calibre binaries aren't in your containers?? o_O Could one of you please navigate to /usr/bin within the container and post the list of binaries there? |
|
Looking for anything specific? That folder is really filled! |
|
There isn't a |
|
Alright I'm not at home atm so not everything works as it should, but I checked the install logs and found two more errors! Maybe this gives some clarification? For some reason copy text is impossible now so I took screenshots:
|
There should be a bunch of binaries in there: calibre If those aren't there that's the issue and I have no idea why they aren't there when they come with the image |
|
Those files aren't in |
|
I have the same problem on Unraid, CWA ingest books but they not appear in Calibre or in CWA GUI, they are simply...i don't know where. |
|
Hello! I also feel like the issue is the third line in the logs, when fetching the book. As @iroQuai said, the calibre binaries are not in /usr/bin but in app/calibre, im pretty sure my compose file is configured properly but I'm including it as well just in case The database also hasn't grown or changed.. I hope this helps figure out whats wrong!! |
|
@iroQuai @Malek-GHub Okay wierd, I have no idea why the binaries would be end up in a seperate folder on synology machines. Could one of you please try the following commands in the containers command line?
If running |
|
Hello @crocodilestick |
|
Same results as @Malek-GHub here! @crocodilestick is there something we can do to help test? Or is this enough info for you to create some kind of a fix? |
|
@iroQuai @Malek-GHub working on a fix now, it worries me that Could you both try running the command |
|
Maybe it's an idea to post the issue here? https://github.com/linuxserver/docker-mods |
|
I can confirm the same issue on my Synology DS920+ with DSM 7.2.1-69057 Update 5 using the following config for docker: docker run -d --name=calibre-web-automated |
|
Ran into this issue, both with plain Calibre web & this container. Found the following: |
|
I’d be more than happy to have a remote session on my Synology and test with somebody, if anyone is interested…. |
|
any fix soon.? |
So, I did move my instance from an older CentOS7 box (3.10 kernel?) to a new Ubunutu 24.04 box - it just works(tm). |
crocodilestick
changed the title
|
Could anyone with a Synology server provide the logs of the docker container right when it gets created from scratch? should be in |
|
@crocodilestick this isn't only with synology, with unraid's docker you can't too |
|
Here's the docker logs from my container on centos7 that was experiencing the same issue. |
|
Here are my logs I'm on a Synology DS220+ with the latest DSM Edit: @crocodilestick current title isn't completely true! CWA is on Synology does work, and is still the better alternative even without the automatic bulk import! The fact I can edit the epub metadata from the webGUI is a big plus! |
Just for folks who are in the same boat and running on an older linux kernel like synology. The fix is mentioned at the bottom of the link and I'll repost it here: use DOCKER_MODS=lscr.io/linuxserver/mods:universal-calibre-v7.16.0. No idea how this will affect things moving forward but it seems to fix the issue in the short term. |
Not functionnal on Unraid |
Can confirm this works on Synology! Thank you! |
|
Holy crap it does work! thanks a lot. This is great!! (Synology ds220+ latest DSM) |
|
For me, it is not working. But when starting I get |
|
I didn't copy the last . In the docker mod URL. Maybe try that?
|
|
Thanks. Sometimes a dot changes a lot :) |
|
it's functionnal but now all book go to /var/lib/docker/volumes/fc0aecf70610b14ac58152771ea7e6259fdde12437f5482d2898dd42da75c6f6/_data instead calibre library when CWA ingest them. |
|
It works!! Although it cant find any book covers and when I mass dumped a bunch of books it stopped at 26 and wont do the rest, even after I refreshed the library... |
|
Choose the edit metadata option after selecting a book. There you can add a cover manually or retrieve one when grabbing all metadata from a source. |
|
Not working for me on Unraid, even with the versioned Docker Mod, the binaries don't get installed. Is there anyway to install them manually for now? EDIT I used the v7.16.0 mod (Not sure if that was needed) apt update Finally updated the path to binaries to /app/calibre and restarted docker |
@iroQuai @inkanyamba @Malek-GHub This is amazing! I'm so glad you guys managed to find a fix! I've updated the README and the |
After upgrading to v2.0.1, books seem to be ingested and are deleted from the ingest folder as expected, but they are not moved to the library. This functionality was working in v1.2.2. Any help would be greatly appreciated!
Dockerfile:
Log:
The text was updated successfully, but these errors were encountered: