Closed glc650 closed 2 years ago
From your provided log it looks like a permission problem at the download-folder location.
The script under '/root/etc/cont-init.d/20-config' can't execute the first mkdir-command and exits with this error:
[cont-init.d] 20-config: exited 1.
I would make sure the docker service has enough permission to create the download and watch folders at the specified locations.
Ok so that's odd because the download directory that I actually have configured isn't /downloads/complete (it's /downloads/_downloading) and this is where the data for the downloads gets saved without issue (so permissions are correct). It is also where the watch directory is. And I don't use a directory for incomplete files (the option is unchecked) so I don't know why it is referencing that.
Changing the default paths of the directories (download, incomplete, watch and config) inside settings.json is currently not supported as far as I understand it.
This means the volume paths should be mounted as recommended in the README and the default filepaths inside settings.json should not be changed.
Without using the default paths the script '/root/etc/cont-init.d/20-config' can't finish properly, which has the consequence of not setting the correct folder ownership with the last 'chown' command.
There are two ways I know to solve the issue. Either use the default folder paths or rewrite the 20-config script to use own paths.
What lines would I have to edit in 20-config?
I don't use complete and incomplete directories. I let sonarr/radarr handle the download when completed.
My downloads dir is the root and inside there I have 3 other directories - movies, TV and _downloading.
TV/movies is strictly for sonarr/radarr. _downloading is where transmission stores its downloads until complete (at which point sonarr/radarr take over).
Line {5} and lines {41-44}. You can probably figure out the rest.
I removed/modified those lines but it didn't make a difference. My watch-dir is a network share and that seems to be the issue (although it worked this way until recently). I've since changed my watch-dir to a local folder and now it works.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I cannot replicate this, the watch directory works as expected.
Expected Behavior
.torrent/.magnet files added to watch-dir should be auto added to transmission queue
Current Behavior
.torrents found in my watch-dir are ignored (transmission doesn't auto add them to queue)
Steps to Reproduce
Environment
OS: Ubuntu 20.04.2 LTS CPU architecture: x86_64 How docker service was installed: from the official docker repo
Command used to create docker container (run/create/compose/screenshot)
docker-compose up In the docker-compose.yml under the volumes section my watch-dir is mapped to /watch (/mnt/downloads/_downloading/_blackhole/_tm:/watch). I also tried editing watch-dir in settings.json but that always seem to get overwritten with /watch
Docker logs
`[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing...
Brought to you by linuxserver.io
To support LSIO projects visit: https://www.linuxserver.io/donate/
GID/UID
User uid: 1000 User gid: 1000
[cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... mkdir: cannot create directory ‘/downloads/complete’: Permission denied mkdir: cannot create directory ‘/downloads/incomplete’: Permission denied chown: cannot access '/downloads/complete': No such file or directory chown: cannot access '/downloads/incomplete': No such file or directory [cont-init.d] 20-config: exited 1. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [2021-06-21 16:41:11.054] Transmission 3.00 (bb6b5a062e) started (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/session.c:769) [2021-06-21 16:41:11.054] RPC Server Adding address to whitelist: 10.0.0.32 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2021-06-21 16:41:11.054] RPC Server Adding address to whitelist: 10.1.0.4 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2021-06-21 16:41:11.054] RPC Server Adding address to whitelist: 10.1.0.31 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2021-06-21 16:41:11.054] RPC Server Adding address to whitelist: 10.1.0.32 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2021-06-21 16:41:11.054] RPC Server Adding address to whitelist: 10.1.0.33 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2021-06-21 16:41:11.054] RPC Server Adding address to whitelist: 10.71.87. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2021-06-21 16:41:11.054] RPC Server Adding address to whitelist: 10.87.77. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2021-06-21 16:41:11.054] RPC Server Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1243) [2021-06-21 16:41:11.054] RPC Server Whitelist enabled (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1249) [2021-06-21 16:41:11.054] Port Forwarding Stopped (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:196) [2021-06-21 16:41:11.054] DHT Reusing old id (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:383) [2021-06-21 16:41:11.054] DHT Bootstrapping from 207 IPv4 nodes (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:172) [2021-06-21 16:41:11.054] Using settings from "/config" (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:646) [2021-06-21 16:41:11.054] Saved "/config/settings.json" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/variant.c:1221) [2021-06-21 16:41:11.054] Watching "/watch" for new .torrent files (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:698) [2021-06-21 16:44:13.051] web will verify tracker certs using envvar CURL_CA_BUNDLE: none (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:455) [2021-06-21 16:44:13.051] web NB: this only works if you built against libcurl with openssl or gnutls, NOT nss (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:457) [2021-06-21 16:44:13.051] web NB: invalid certs will show up as 'Could not connect to tracker' like many other errors (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:458)`