OMV5 + Transmission - Invisible download location

    Hello,


    I recently installed OMV5 as a first time DIY server user and managed to get it working for the most part.
    My shared folders are up and running, I have installed plex which recognizes all my files but I can't get Transmission to work properly.


    I followed the Technodad guide for Qbittorrent but used the linuxserver/transmission container instead. Installation seems to have gone good.
    I can log in the GUI and download torrent files (which actually complete and start seeding) but I can't for the life of me find my downloaded files.
    Initially I figured this must have something to do with the UMASK_SET since Technodad included this environment (022) so I restarted and edited the container and added the maskset to no avail.
    I started new torrent files which still download without problems but I can't find the correct folder.


    Initially the download folder for Transmission was set to "/Downloads/Complete" which I have changed to "/Downloads". I assumed this would download my files to:
    "/srv/dev-disk-by-label-Storage/NAS/Downloads"


    In OMV5 under File Systems I can see the available storage decrease with each download so it's storing it to the correct drive.
    Can anyone point me in the right direction? I'm happy to figure these things out myself but I'm really at a loss here.


    Thank you in advance!


    Edit1: I have added a screenshot of the ENV settings in Portainer. Could it be that Transmission is downloading these files to /root/Downloads rendering the download location invisible? If so, is there any way to change this?

    Did you set an explicit bind mount for your downloads in the docker configuration? This is NOT set in the Environment table. It's in the Volumes tab under Advanced container settings.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Gefällt mir 1

    First thing to do is review the log for the container.


    Does the user (1000) have write access to the Host volume pointed to by the /downloads Path in container?


    In the Transmission GUI, exactly what are you specifying for the downloads location? (It's case sensitive)

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Gefällt mir 1

    Hi gderf,


    Stupid question, what am I looking for specifically in the log file? I posted a screenshot below.
    As for the download location in the GUI: "/downloads" while the actual folder on the NAS is /Downloads with a capital D.


    Thanks again for putting your time into this!


    Edit: I have changed the folders to "/downloads" (lower case) which didn't help.


    Edit 2: In the log I can see the download starts and when completed the state is changed from incomplete to complete. However, I note the following error:


    [2020-01-02 19:13:29.965] Couldn't create "/Downloads": Permission denied (file-posix.c:189)

    Well, the log looks OK, but I'm basing that on the lack of warnings or errors. I don't use Transmission myself, but I was able to quickly create a docker of it and it worked fine.


    Look in the directory that is pointed to by /downloads. Once you add and start a torrent two directories should be created there, /complete and /incomplete. Are those there?

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Gefällt mir 1

    Gderf,


    Those folders are not there, instead I get the permission error as described in the edit above. In openmediavault I can't seem to find transmission under ACL to provide read/write access. I am currently using this guide:


    https://forum.openmediavault.o…n-plugin-for-permissions/


    Could this be the problem?


    Edit: I don't understand that the torrents download while the folders seemingly can't be created. Is there any easy way I can provide you with the full log?

    Also a hint for you. When I want to very quickly deploy a new container I like to use Portainer's Stack feature. I add a new stack and paste in a docker compose file (must be version 2) into the box and edit it to suit my needs. Then I deploy the stack. Once it is running error free, the image is pulled and the container is automatically created for you. Below I the quickie I used, based on what is available for the image on linuxserver.io. All I did was edit the few lines that needed to be changed.


    ---
    version: "2"
    services:
    transmission:
    image: linuxserver/transmission
    container_name: transmission
    environment:
    - PUID=1001
    - PGID=100
    - TZ=America/New_York
    - USER=username #optional
    - PASS=password #optional
    volumes:
    - /srv/dev-disk-by-label-d4/docker-config/transmission:/config
    - /srv/dev-disk-by-label-d1/sftp/incoming:/downloads
    - /srv/dev-disk-by-label-d1/sftp/incoming:/watch
    ports:
    - 9091:9091
    - 51413:51413
    - 51413:51413/udp
    restart: unless-stopped

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Einmal editiert, zuletzt von gderf ()

    Dockers are extremely sensitive to permissions problems. I don't use the OMV ACL/Permissions pages to set them, I do it by hand in the shell, but it's rare that I need to do this as all my dockers run as an already existing user on the system and that user already has the correct permissions for the areas my dockers operate on and in. So I don't need to so anything with permissions when adding new containers


    You need to check the permissions of these areas in the shell and make sure that the user the container is running as has read and write access.


    As for torrents apparently downloading but not appearing where you expect them to, they are probably defaulting to a location within the running container itself, and this area is not convenient to access.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Einmal editiert, zuletzt von gderf ()

    Hi Gderf,


    I have no experience using stacks nor do I have any experience using OMV or Portainer for that matter so I'm tweaking things based on old guides due to lack of newer ones.
    I have tried another torrent to see what the logs say, this time using download location /nas/downloads and I get the following log:


    I can see that Transmission saves the .torrent file on my NAS.


    Knowing this, could you point me to a guide to check (and change) the permissions in the shell?


    Thanks again for your help and pointing me in the right direction.


    [2020-01-02 20:04:13.973] Saved "/config/torrents/Vikings.S06E02.HDTV.x264-SVA.577e5de07ed9cc44.torrent" (variant.c:1266)
    [2020-01-02 20:04:13.974] Vikings.S06E02.HDTV.x264-SVA Queued for verification (verify.c:269)
    [2020-01-02 20:04:13.974] Vikings.S06E02.HDTV.x264-SVA Verifying torrent (verify.c:224)
    [2020-01-02 20:04:23.975] Saved "/config/torrents/Vikings.S06E02.HDTV.x264-SVA[eztv].mkv.577e5de07ed9cc44.torrent" (variant.c:1266)
    [2020-01-02 20:04:23.975] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Pausing (torrent.c:1856)
    [2020-01-02 20:04:23.975] Saved "/config/resume/Vikings.S06E02.HDTV.x264-SVA[eztv].mkv.577e5de07ed9cc44.resume" (variant.c:1266)
    [2020-01-02 20:04:23.975] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Magnet Verify (torrent.c:1879)
    [2020-01-02 20:04:23.975] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Queued for verification (verify.c:269)
    [2020-01-02 20:04:23.975] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Verifying torrent (verify.c:224)
    [2020-01-02 20:04:25.967] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Starting IPv4 DHT announce (firewalled, 176 nodes) (tr-dht.c:575)
    [2020-01-02 20:05:18.962] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Connection failed (announcer.c:996)
    [2020-01-02 20:05:18.962] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Retrying announce in 20 seconds. (announcer.c:1005)
    [2020-01-02 20:05:18.962] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Could not connect to tracker (announcer.c:996)
    [2020-01-02 20:05:18.962] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Retrying announce in 20 seconds. (announcer.c:1005)
    [2020-01-02 20:05:23.959] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Connection failed (announcer.c:996)
    [2020-01-02 20:05:23.959] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Retrying announce in 20 seconds. (announcer.c:1005)
    [2020-01-02 20:05:38.955] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv State changed from "Incomplete" to "Complete" (torrent.c:2216)
    [2020-01-02 20:05:38.955] Couldn't create "/nas": Permission denied (file-posix.c:189)
    [2020-01-02 20:05:38.955] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv moving "/downloads/incomplete/Vikings.S06E02.HDTV.x264-SVA[eztv].mkv" to "/nas/downloads/Vikings.S06E02.HDTV.x264-SVA[eztv].mkv" (torrent.c:3157)
    [2020-01-02 20:05:38.955] Couldn't create "/nas": Permission denied (file-posix.c:189)
    [2020-01-02 20:05:38.955] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv error moving "/downloads/incomplete/Vikings.S06E02.HDTV.x264-SVA[eztv].mkv" to "/nas/downloads/Vikings.S06E02.HDTV.x264-SVA[eztv].mkv": Unable to create directory for new file: Permission denied (torrent.c:3161)
    [2020-01-02 20:06:39.962] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Connection failed (announcer.c:996)
    [2020-01-02 20:06:39.962] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Retrying announce in 316 seconds. (announcer.c:1005)
    [2020-01-02 20:06:39.962] Vikings.S06E02.HDTV.x264-SVA[eztv].mkv Could not connect to tracker (announcer.c:996)

    I suggest deleting the container and starting over with the stack template I provided, but do make any needed changes. Look carefully at every line.


    In Portainer there is a Stacks menu item on the left. Click there, then click the Add stack button. At the top give the stack a name - transmission, In the web editor box, past in the template I provided and make all needed changes to it - look at every single line. Then scroll to the bottom of the page and hit the Deploy the stack button. If errors pop up, solve them and try again. Once it's running successfully go to the Transmission page in your browser, load and start a torrent and see what happens.


    We'll work on permissions next if that problem persists.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Hi Gderf,


    I went ahead and created a "downloads" folder on my drive since replacing it with "nas" wasn't working. It now works perfectly (using Qbittorrent). Not sure what was causing the inability to put them in the NAS folder but I will just do this manually or just map plex to this new folder instead.


    I will try transmission in the same way next assuming this will work as well. I assume the prior downloads are to be stored on my NAS for the rest of its existence or is there a way to remove these?


    Anyway, thank you so much for your help!

    If the misdirected downloads were stored within the container, just delete it and recreate it. 99.40% of docker problems are related to incorrect permissions. It's impossible to stress this point enough.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Gefällt mir 1

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden