(SOLVED) can't locate downloaded files of nzbget - path seems to be ok

[Tyler Durden]

Hey guys,

 

First post and that's because im totally clueless now. Ive been using Unraid for several years with great pleasure.

But somehow, I can't seem to find the problem here.

 

Ive been configuring my new server the last few weeks and now ive been using Deluge and NZBget as download clients and besides that I'm using Sonarr and Radarr to manage them.

 

Somehow I cannot locate my downloaded NZBget files. 

 

Can someone please double check my path mappings.

 

Thank you in advance and I really appreciate all the help I can get.

 

 

Edited May 15, 2021 by Tyler Durden

[trurl]

Mappings are only part of the puzzle. Applications must write to a path that corresponds to a container path. Linux is case-sensitive.

[trurl]

If an application is writing to a path that isn't mapped, it will be writing into docker.img

 

Post diagnostics.

[Tyler Durden]

Just now, trurl said:

If an application is writing to a path that isn't mapped, it will be writing into docker.img

 

Post diagnostics.

Ahaaa, That's why im seeing docker.img utilization is high popup. 

[trurl]

1 minute ago, Tyler Durden said:

Ahaaa, That's why im seeing docker.img utilization is high popup. 

 

4 minutes ago, trurl said:

Linux is case-sensitive.

 

[Tyler Durden]

Here you are sir.

dajjal-diagnostics-20210505-2027.zip

[Tyler Durden]

16 minutes ago, trurl said:

Mappings are only part of the puzzle. Applications must write to a path that corresponds to a container path. Linux is case-sensitive.

 

Good to know that Linux is case-sensitive.

 

Can I get away with it if I mapped them all good? 

 

And from now on, I will not use CAPITAL  

 

Edited May 5, 2021 by Tyler Durden

[trurl]

Just now, Tyler Durden said:

Good to know that Linux is case-sensitive.

 

I can get away with it if I mapped them all good...right? 

 

And from now on, I will not use CAPITAL  

The fact that you did use CAPITAL was one reason I suspected your mistake.

 

As already explained, mapping isn't the whole picture. In fact, there is nothing wrong with those mappings as long as the application actually uses the specified container path.

 

Any path settings WITHIN the application must correspond to a container path.

[Tyler Durden]

10 minutes ago, trurl said:

The fact that you did use CAPITAL was one reason I suspected your mistake.

 

As already explained, mapping isn't the whole picture. In fact, there is nothing wrong with those mappings as long as the application actually uses the specified container path.

 

Any path settings WITHIN the application must correspond to a container path.

 

So I need to edit the pathnames WITHIN nzbget that matches the folders on the 'DOWNLOAD MAINFRAME' folder

 

 

 

[trurl]

I use NZBGet but linuxserver instead of that one.

 

10 minutes ago, Tyler Durden said:

edit the pathnames WITHIN nzbget that matches the folders on the 'DOWNLOAD MAINFRAME' folder

Looks like the container path you have specified is /data. Within the application you haven't told it to use anything since MainDir is just a subfolder of AppDir which isn't mapped (or maybe AppDir corresponds to /config so the downloads would be in appdata).

 

45 minutes ago, Tyler Durden said:

been using Unraid for several years

Did someone else setup your dockers before?

 

[Tyler Durden]

18 minutes ago, trurl said:

I use NZBGet but linuxserver instead of that one.

 

Looks like the container path you have specified is /data. Within the application you haven't told it to use anything since MainDir is just a subfolder of AppDir which isn't mapped (or maybe AppDir corresponds to /config so the downloads would be in appdata).

 

Did someone else setup your dockers before?

 

 

No, i've been doing it different this time with my new server.

What else did you notice about my dockers? Have I been making a terrible mistake?

 

It's my first time using NZBget, I thought I had it all good.

I will change the path mappings and see if there's an improvement.

 

[trurl]

9 minutes ago, Tyler Durden said:

I will change the path mappings

Why? What will you change them to?

 

1 hour ago, trurl said:

there is nothing wrong with those mappings as long as the application actually uses the specified container path.

 

Do you know what I mean by "container path"?

[Tyler Durden]

12 hours ago, trurl said:

Why? What will you change them to?

 

 

Do you know what I mean by "container path"?

 

Ive read it wrong. I definitely know what u mean by 'container path'

I will check it again 

[Tyler Durden]

This has been solved. 

 

Thank you @trurlfor your time

[grayskullduggery]

On 5/16/2021 at 1:57 AM, Tyler Durden said:

This has been solved. 

 

Have a similar issue, and wondering how you solved it @Tyler Durden? 

 

Can you share your exact folder paths in NZBget and container paths?

 

I currently have the default MainDir -> ${AppDir}/downloads in NZBget and /data -> /mnt/user/downloads/ in my container mapping. But suspect this needs to be changed to something like MainDir -> /data in nzbget? 

 

Thanks

[Tyler Durden]

On 10/31/2021 at 12:11 AM, grayskullduggery said:

Have a similar issue, and wondering how you solved it @Tyler Durden? 

 

Can you share your exact folder paths in NZBget and container paths?

 

I currently have the default MainDir -> ${AppDir}/downloads in NZBget and /data -> /mnt/user/downloads/ in my container mapping. But suspect this needs to be changed to something like MainDir -> /data in nzbget? 

 

Thanks

Just read your post. Did you solve it already?

[UmbraSilentium]

Just recently got into Unraid and am having this exact same issue. I've tried all combinations of pathing for NZBGet to no avail. Is there any way I can get some help on this?

[trurl]

4 minutes ago, UmbraSilentium said:

get some help on this?

Post your docker run for the container

[UmbraSilentium]

Apologies, I should have provided this from the beginning, my bad.

 

29 minutes ago, trurl said:

Post your docker run for the container

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='nzbget' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'PUID'='0' -e 'PGID'='0' -e 'UMASK'='022' -p '6789:6789/tcp' -v '/mnt/disk1/UN/':'/downloads':'rw' -v '/mnt/user/appdata/nzbget':'/config':'rw' 'lscr.io/linuxserver/nzbget:latest'

8380fb3b498d8fb7259cde988a166ea50866e4a14de0875d2e43dedd0b537d1e

 

nzbget docker download path: /mnt/disk1/UN/

 

I have a share that I have my media on. Might be my misunderstanding of Unraid as I kind of assumed that the Share was part of my overall Array.

 

NZBGet download completes and shows a successful move of the file, but it's nowhere to be seen. Attaching images of the Share settings, as well as the NZBGet paths. This is just my latest attempt at the paths, I've tried a bunch of different options.

[trurl]

/complete/Movies is not a subfolder of /downloads. Since /complete isn't mapped it is inside docker.img

[UmbraSilentium]

29 minutes ago, trurl said:

Since /complete isn't mapped it is inside docker.img

 

Okay, that's kind of what I had been seeing. What's the best way to fix this? I've tried mapping in NZBGet to just /complete, and that didn't work. I also set the main directory to be /mnt/user/UN/ and then complete to be ${MainDir}/complete and that didn't work either. Thoughts?

 

Edit: Not sure if it makes a difference, but when in Sonarr and trying to import a series, the location that I'm trying to reference in NZBGet isn't visible. Which is why I think there's something weird with the path.

Edited January 20, 2022 by UmbraSilentium

[Squid]

https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-566086

 

[trurl]

11 hours ago, UmbraSilentium said:

Okay, that's kind of what I had been seeing. What's the best way to fix this? I've tried mapping in NZBGet to just /complete, and that didn't work. I also set the main directory to be /mnt/user/UN/ and then complete to be ${MainDir}/complete and that didn't work either.

You seem to be trying things randomly instead of trying to understand how docker volume mapping works.

 

You have mapped /downloads to /mnt/user/UN. NZBGet doesn't know the host path /mnt/user/UN, it just knows the container path that has been mapped to, /downloads. So, MainDir would be /downloads, and DestDir would be a subfolder of that, ${MainDir}/complete.

 

As for getting different dockers to work together, these applications are telling each other where to put and look for files. They must specify a path that both understands, which means the container paths they are each using must be the same, and must map to the same host path.

[UmbraSilentium]

Thank you both for the replies, truly appreciate it.

 

Referring to the link that @Squid posted, that was helpful with examples of pathing. Is there any concern however with running the config files off of the Cache? Additionally, will the downloaded files migrate over to the array once the mover is invoked?

 

@trurl, that makes sense and is also definitely what I was doing, so apologies. I'm new to Unraid and dockers, so I'm a little in over my head. The host location and everything makes sense I think. The downloads and everything go straight to the Cache though, so could I technically do something like /mnt/disk/UN/appdata/nzbget (or Sonarr, Couchpotato, etc) for the docker host location (for the config file); then do /mnt/disk/UN/download for the location of the downloads in the docker pathing? Then do /downloads for MainDir and ${MainDir}/completed for the final files?

 

Sorry, just trying to wrap my head around this. Additionally, when in Couchpotato or Sonarr and going to select the location for renaming, the file browser shows nothing when it's in the /mnt location.

[trurl]

1 hour ago, UmbraSilentium said:

Is there any concern however with running the config files off of the Cache?

Many dockers have a /config (or similar) mapping to the appdata share. User shares are at /mnt/user (not /mnt/disk), so appdata is at /mnt/user/appdata. The appdata share is where containers keep their "working data", such as any settings you make within an application.

 

There is also the system share, which is usually where docker.img and libvirt.img are kept. docker.img contains the executable code of your containers.

 

And there is the domains share where VM virtual disks are kept.

 

Ideally, appdata, domains, and system shares will be on fast pool (cache) and set to stay there (prefer or only), so dockers/VMs will perform better and not keep array disks spunup, since these files are always open.

 

Personally, I don't like downloading into a subfolder of appdata, because you need to have backups of appdata (CA Backup plugin) and no good reason to have the downloads included in that. So, a separate download share makes sense, which would be at /mnt/user/download (not /mnt/disk/download).

 

You seem to be thinking about some user share named UN that everything goes in, but I don't like that idea either. Different shares with different settings for different purposes. Some need to stay on fast pool, some need to be on the array or moved to the array from fast pool, and there will be other settings for each user share that are appropriate for different purposes.

 

1 hour ago, UmbraSilentium said:

when in Couchpotato or Sonarr and going to select the location for renaming, the file browser shows nothing when it's in the /mnt location

containers don't know anything about host paths, they only know about container paths. In order for an application to see anything on host storage, it must be through a container path mapped to a host path. Since each container is a little self-contained linux, it will have linux paths inside it, but these don't correspond to any host paths unless mapped. So, /mnt is likely empty inside the container, and has nothing at all to do with the host path /mnt.