I am mounting rclone crypt remote to /home/ubuntu/mnt/gcrypt. The mount is working as expected and I can see all the folders/files inside, but my docker container Plex is unable to see anything inside the mount when I bind the volume.
I'm trying to figure out where the issue is. I thought it may be permissions so I made sure the systemd mount service has allow-other and umask 000 (I've tried 002 as well) set. I also exec'd into container and saw that the container can indeed see /plexmedia folder but inside there is nothing (even though there should be Movies, TV Shows, 4K, 4K TV, etc). Not sure where else to go from here but I can't seem to narrow it down.
Yeah that's pretty the same way I have mine set up currently.
I was able to solve this by switching straight to /mnt/gcrypt as the mountpoint instead of ~/mnt/gcrypt. I 775'd the /mnt so it could be seen regularly. Not sure if this is best practice but after restarting the service and plex I was able to finally see gcrypt inside Plex's docker container.
That is solved but now I am having the issue of the rclone mount essentially stalling out after a little bit of time. I've tried enabling logging to a log-file but I get nothing written to any log file. Is that again a permissions thing or what?
@ncw - thanks for your earlier suggestions, see this update.
The service was under --user and I just moved it into /etc/systemd and re-did everything, rebooted, and here is the output from journalctl -u gcrypt -b | less.
Just a note: | less is used to wrap lines instead of truncating in terminal.
-- Logs begin at Tue 2021-09-07 18:37:22 UTC, end at Fri 2022-12-09 19:52:29 UTC. --
Dec 09 19:51:19 arm systemd: Starting GCrypt...
Dec 09 19:51:21 arm systemd: Started GCrypt.
Generally, that means either your service file doesn't have a log file in it, you didn't reload the service file or something along those lines.
If you are sure that's the right service file, it'll fail to start if it can't write the log file.
Would look like:
root@gemini:/etc/systemd/system# vi test.service
root@gemini:/etc/systemd/system# systemctl daemon-reload
root@gemini:/etc/systemd/system# systemctl start test
Job for test.service failed because the control process exited with error code.
See "systemctl status test.service" and "journalctl -xeu test.service" for details.
root@gemini:/etc/systemd/system# journalctl -u test -b
Dec 09 17:07:51 gemini systemd: Starting test...
Dec 09 17:07:51 gemini rclone: 2022/12/09 17:07:51 Failed to open log file: open /wrong/fake/test.log: no such file or directory
Dec 09 17:07:51 gemini systemd: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 09 17:07:51 gemini systemd: test.service: Failed with result 'exit-code'.
Dec 09 17:07:51 gemini systemd: Failed to start test.