[Support] Linuxserver.io - NZBGet


461 posts in this topic Last Reply

Recommended Posts

You should be fine to keep your existing config, just point the appdata path to the same place.  Stop the old docker first of course, and perhaps take a backup of the appdata just in case of any weirdness.

 

Have done this a couple times myself with no issues in any case.

Link to post
  • 3 weeks later...
  • Replies 460
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: NZBGet Application Site: http://nzbget.net/ Docker Hub: https://hub.docker.com/r/linuxserver/nzbget/ Github: https://github.com/linuxserver/docker-nzbget   P

Thank you CHBMB!   To summarize, in NZBGet go to: Settings  > Extensions Scripts. In the field labeled ShellOverride enter the following: .py=/usr/bin/python3 This worked perfectly

I was so focused on the download path that I didn't realize it was my category paths that were screwing me up.   Everything is finally working now.   Thanks for the help trurl!  I've been working on t

Posted Images

  • 4 weeks later...
  • 3 weeks later...

I posted this on /r/unraid but I figure I might try and get some help here too. 

 

I need some helping figuring out how to stop NZBGet from making my server completely unresponsive when it is working. I can't load unRAID's GUI nor can I access any docker containers when it is downloading. Shortly after a download is initiated, the cpu usage spikes to 100% and I am locked out until NZBGet completes its tasks. I've tried restricting NZBGet to 4Gb of memory and 1 of the 4 cores via --cpuset-cpus=0 --memory=4G. According to "docker stats" the memory is restricted correctly, but it still utilized all 4 of the available cores. Does anybody have an idea how to stop this issue?

 

Also, NZBGet downloads and unpacks to the cache SSD drive and not the array.

 

M/B: ASRock - H97M-ITX/ac CPU: Intel® Core™ i5-4460 CPU @ 3.20GHz

Link to post
5 hours ago, osker246 said:

I posted this on /r/unraid but I figure I might try and get some help here too. 

 

I need some helping figuring out how to stop NZBGet from making my server completely unresponsive when it is working. I can't load unRAID's GUI nor can I access any docker containers when it is downloading. Shortly after a download is initiated, the cpu usage spikes to 100% and I am locked out until NZBGet completes its tasks. I've tried restricting NZBGet to 4Gb of memory and 1 of the 4 cores via --cpuset-cpus=0 --memory=4G. According to "docker stats" the memory is restricted correctly, but it still utilized all 4 of the available cores. Does anybody have an idea how to stop this issue?

 

Also, NZBGet downloads and unpacks to the cache SSD drive and not the array.

 

M/B: ASRock - H97M-ITX/ac CPU: Intel® Core™ i5-4460 CPU @ 3.20GHz

 

I haven't used cpu pinning for dockers, but there should be some info in the docker faq. Looks wrong with the s at the end of cpu though. 

 

If it's unpacking to the cache drive, you have your volume mapping or share settings wrong. You need to post your docker run command and post a screenshot of the share settings for the shares you use. 

Link to post
8 hours ago, osker246 said:

ccording to "docker stats" the memory is restricted correctly, but it still utilized all 4 of the available cores

Docker stats does not display the core(s) the container is able to run on.  If you are looking at the CPU%, then the percentage on a 4 core system goes from 0 up to 400%.

 

Best way to see core usage is either through the NetData app, or cAdvisor app

2 hours ago, saarg said:

Looks wrong with the s at the end of cpu though

The s is correct

Link to post
5 hours ago, Squid said:

Docker stats does not display the core(s) the container is able to run on.  If you are looking at the CPU%, then the percentage on a 4 core system goes from 0 up to 400%.

 

Best way to see core usage is either through the NetData app, or cAdvisor app

The s is correct

I blame a few of these for my mistake... 

 

1529669633481.jpg

Link to post
1 hour ago, CHBMB said:

Stella Artois, colloquially known as wife beater in the UK, due to the effect it has on some of the less respectable members of the population who drink it to excess.......

 

Good thing I didn't drink too much then, as my better half would have beaten me senseless if I tried beating here.... ?

Link to post
15 hours ago, saarg said:

 

If it's unpacking to the cache drive, you have your volume mapping or share settings wrong. You need to post your docker run command and post a screenshot of the share settings for the shares you use. 

Here is my volume mappings and download shares. I'm not quite sure where or what the the docker run command is. Care to elaborate where I can find this information?

 

I should also say that I did a reinstall on the unRAID OS, wiped the cache drive, and did a fresh install of all containers and plugins and the issue is still persisting. 

Container paths.JPG

download share.JPG

Link to post

How to find the docker run command is in my signature. You need to turn those on in your control panel if you don't see them. 

 

But I see that you have set the share to only use the cache drive and also the path in the container template is set to /mnt/cache. 

If you want the files to be on the array, you need to change the share to either cache: yes or cache: no. 

Set it to yes if you want it to download to the cache first and then moved to the array by the mover. 

Set it to no if you want the files downloaded to the array. 

Link to post
  • 2 weeks later...

Hi All,

Wondering if anybody else is seeing this/has any suggestions:
Basically, NZBget is working perfectly, happily downloading and process files UNTIL mover starts.  As soon as mover starts, it throws error after error like this: [ERROR] Could not create file /downloads/tmp/nzb-24.tmp

 

As soon as mover stops, the errors stop and all is well.  I can't restart or do anything with the container during the mover operation.  

I've got it mapped like this:
/downloads /mnt/cache/downloadsfolder

/config /mnt/user/appdata/nzbget

 

Any ideas?

thank you!

Link to post
1 hour ago, mbezzo said:

Hi All,

Wondering if anybody else is seeing this/has any suggestions:
Basically, NZBget is working perfectly, happily downloading and process files UNTIL mover starts.  As soon as mover starts, it throws error after error like this: [ERROR] Could not create file /downloads/tmp/nzb-24.tmp

 

As soon as mover stops, the errors stop and all is well.  I can't restart or do anything with the container during the mover operation.  

I've got it mapped like this:
/downloads /mnt/cache/downloadsfolder

/config /mnt/user/appdata/nzbget

 

Any ideas?

thank you!

 

What is  the Use cache setting for your User Share named downloadsfolder?

Link to post

I'm new (Very) to unRAID and just had a thought.  If cached is off for the downloadsshare, but I point the container to /mnt/cache/downloadsfolder - that would still be writing to the cached SSD's, right? 

 

I think this concept is what's confusing me...  If I had caching ON and pointed to /mnt/user/downloadsfolder - that'd be effectively the same as caching off, but then pointing to /mnt/cache/downloadsfolder?

 

Appreciate the help!

 

Link to post
On 7/3/2018 at 10:33 PM, mbezzo said:

I'm new (Very) to unRAID and just had a thought.  If cached is off for the downloadsshare, but I point the container to /mnt/cache/downloadsfolder - that would still be writing to the cached SSD's, right? 

 

I think this concept is what's confusing me...  If I had caching ON and pointed to /mnt/user/downloadsfolder - that'd be effectively the same as caching off, but then pointing to /mnt/cache/downloadsfolder?

 

Appreciate the help!

 

 

The good thing is you dont need to understand it to use it. Just add shares for everything youll add, make the correct cache settings like u want, and point it to /mnt/user/sharename ... 

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.