binhex Posted July 30, 2018 Author Share Posted July 30, 2018 ahh i spotted it, new image created, please pull down. Quote Link to comment
rmilyard Posted July 30, 2018 Share Posted July 30, 2018 I have a noob question. I think I have the latest version but is there a way to check what version of docker file running? Quote Link to comment
Splatman2 Posted July 31, 2018 Share Posted July 31, 2018 8 hours ago, binhex said: ahh i spotted it, new image created, please pull down. Thank you very much Binhex That fixed them up. GUI is back. 1 Quote Link to comment
david_waters Posted July 31, 2018 Share Posted July 31, 2018 (edited) Maybe dumb question. I am trying to install the videosort extension. Where exactly is my pp-scripts directory? I have been hunting for it for an hour now. thank you edit - right after writing this and i closed the tab, boom it was right there in the paths section of the settings but can not figure out where that is on my box it says: ${AppDir}/scripts Edited July 31, 2018 by david_waters Quote Link to comment
ajgriglak Posted August 14, 2018 Share Posted August 14, 2018 Hey guys... this container has been rock solid since I installed it! Thanks, Binhex... I finally resolved my slow internet speed and went from 30 MBps to 320 MBps. To celebrate, I decided to hit the "Search All Missing" button in Sonarr. Now I have about 600 items downloading. When the queue was lower, like 50 and less, I could get downloads in unlimited speed limit at about 30 MBps. Now that the queue is huge, it's slowed down to about 5 MBps. Has anyone seen this issue? Any tweaks in container setup or NZBGet settings to alleviate the throttling? Quote Link to comment
ajgriglak Posted August 14, 2018 Share Posted August 14, 2018 On 7/31/2018 at 1:58 PM, david_waters said: Maybe dumb question. I am trying to install the videosort extension. Where exactly is my pp-scripts directory? I have been hunting for it for an hour now. thank you edit - right after writing this and i closed the tab, boom it was right there in the paths section of the settings but can not figure out where that is on my box it says: ${AppDir}/scripts I just tried looking for mine, and there is no scripts folder in my setup (I don't use scripts, though). Maybe you need to manually create it? Quote Link to comment
Cessquill Posted August 15, 2018 Share Posted August 15, 2018 14 hours ago, ajgriglak said: Now I have about 600 items downloading. When the queue was lower, like 50 and less, I could get downloads in unlimited speed limit at about 30 MBps. Now that the queue is huge, it's slowed down to about 5 MBps. Has anyone seen this issue? Any tweaks in container setup or NZBGet settings to alleviate the throttling? Once something has downloaded, Sonarr will make a backup copy of it, copy that backup into the correct location and then delete the originals. This overhead *could* slow down your downloads - especially if you are downloading straight the unraid array (ie, not onto a cache drive) as they will be competing for use of the parity drive. OR, your ISP might be throttling your connection. Just a couple of thoughts. Quote Link to comment
ajgriglak Posted August 15, 2018 Share Posted August 15, 2018 4 hours ago, Cessquill said: Once something has downloaded, Sonarr will make a backup copy of it, copy that backup into the correct location and then delete the originals. This overhead *could* slow down your downloads - especially if you are downloading straight the unraid array (ie, not onto a cache drive) as they will be competing for use of the parity drive. Thanks for your reply. I download directly to a 1TB Unassigned Drive (not SSD). Your mention of parity got me thinking... I was also in the middle of a parity check, so maybe that had something to do with it. The parity check is now done, and it has been running overnight. It's now fluctuating between 15 and 30 MBps, so definitely more acceptable. I just thought maybe there was some tweaks that could be done when the queue is so large. Quote Link to comment
Cessquill Posted August 15, 2018 Share Posted August 15, 2018 I've not heard of any difference from queue size FWIW, but a parity check can slow down a lot of things. Even if it's not part of the array, the parity traffic will still make an impact. Quote Link to comment
Cessquill Posted September 4, 2018 Share Posted September 4, 2018 On 7/30/2018 at 6:09 PM, rmilyard said: Do you know if the part for unpacking files and deleting it and doing it again in endless loop was fixed? Hi - just realised I'm still on the old version of this. Is it still stuck in a loop on unpacking? If it means setting and testing for max limits I might stay where I am for now - save that for a weekend job. Quote Link to comment
binhex Posted September 5, 2018 Author Share Posted September 5, 2018 17 hours ago, Cessquill said: Hi - just realised I'm still on the old version of this. Is it still stuck in a loop on unpacking? If it means setting and testing for max limits I might stay where I am for now - save that for a weekend job. last i heard there was still issues around unpacking, i have seen a test release of nzbget has been released and there was a fair bit of detail around par and crc checking and such like in the next release, so possibly the next release will fix this up, we shall see. 1 Quote Link to comment
rmilyard Posted September 20, 2018 Share Posted September 20, 2018 binhex and news on the unpacking issues? I would like to update from 19.1 which is last version that seems to work all the time. Quote Link to comment
binhex Posted September 21, 2018 Author Share Posted September 21, 2018 11 hours ago, rmilyard said: binhex and news on the unpacking issues? I would like to update from 19.1 which is last version that seems to work all the time. still the same situation as my previous post im afraid. Quote Link to comment
boomsmcg Posted October 6, 2018 Share Posted October 6, 2018 Has anyone written a script that can detect the unpacking crash and automatically restart the docker as a work around for now? Quote Link to comment
puncho Posted October 6, 2018 Share Posted October 6, 2018 Hi, I've been having the unpacking/download queues problem for a few months and never got around to fixing it until now. Looking at it, seems like it's best to roll back to v19.1-1-02. I did so by following the Q12 on the link provided by editing the repository end. Now, when I try to access the webUI, I get that "Error: 404 Not Found". I thought that problem was fixed? I went into the nzbget.conf file and looked for the WebDir=/usr/share/nzbget/webui, but only see WebDir={AppDir}/webui. Am I supposed to change that to WebDir=/usr/local/bin/nzbget/webui? thanks! Quote Link to comment
puncho Posted October 17, 2018 Share Posted October 17, 2018 On 10/6/2018 at 3:26 PM, puncho said: Hi, I've been having the unpacking/download queues problem for a few months and never got around to fixing it until now. Looking at it, seems like it's best to roll back to v19.1-1-02. I did so by following the Q12 on the link provided by editing the repository end. Now, when I try to access the webUI, I get that "Error: 404 Not Found". I thought that problem was fixed? I went into the nzbget.conf file and looked for the WebDir=/usr/share/nzbget/webui, but only see WebDir={AppDir}/webui. Am I supposed to change that to WebDir=/usr/local/bin/nzbget/webui? thanks! Nzbget is working well but still can't get into the webui...any clues? :) Quote Link to comment
KernelG Posted October 17, 2018 Share Posted October 17, 2018 On 10/6/2018 at 12:26 PM, puncho said: Now, when I try to access the webUI, I get that "Error: 404 Not Found". I did the same thing, attempting the latest new build and reverting to v19.x, only to find a 404 error where the web UI used to be. I also tried editing the .conf file, but had no luck. I ended up pulling a copy of the .conf file from the previous week's backup, and now all is well again on v19. If it helps, my line 64 of that file is currently: WebDir=/usr/share/nzbget/webui Quote Link to comment
puncho Posted October 23, 2018 Share Posted October 23, 2018 On 10/17/2018 at 2:40 PM, KernelG said: I did the same thing, attempting the latest new build and reverting to v19.x, only to find a 404 error where the web UI used to be. I also tried editing the .conf file, but had no luck. I ended up pulling a copy of the .conf file from the previous week's backup, and now all is well again on v19. If it helps, my line 64 of that file is currently: WebDir=/usr/share/nzbget/webui Thanks. Not a huge deal right now I guess...I'll wait till it's fixed in the future. Quote Link to comment
Tunatuk Posted November 14, 2018 Share Posted November 14, 2018 So I'm having an issue that I can't quite figure out. I have previously used NZBGet on Windows, and got an unRaid server going. Installed it, and I'm probably doing something stupid, but unpacking fails every time I try and download something. I have my data path set to /mnt/user/Downloads/ In the NZBget UI, I have my paths set up as: MainDir: /data DestDir: ${MainDir}/Completed InterDir: ${MainDir}/intermediate NzbDir: ${MainDir}/nzb QueueDir: ${MainDir}/queue TempDir: ${MainDir}/tmp WebDir: ${AppDir}/webui Whenever I download a file from usenet, two things happen. My main provider (Eweka gets blocked for 10s for some reason, but a test in settings works, and I'm able to log in just fine), and it fails to unpack upon completion. I get the error message Unpack for XXXXXXX (whatever the file name is) failed. It passes verification, says that no repair is needed, but then fails the unpack, and adds the file to the registry. Can anyone provide me any guidance? Quote Link to comment
Cessquill Posted November 14, 2018 Share Posted November 14, 2018 Unpacking is broken in the current version. Scroll back in this post to around June to see how to install previous versions. Quote Link to comment
repomanz Posted January 8, 2019 Share Posted January 8, 2019 while unpacking; seems it does not honor cpu pinning. IE; even though i have cpu 1,5 pinned, it's maxing out all of my cpus. Seeing above posts are there plans to fix unpacking issues? Other issues i have with unpacking is that it hangs or takes forever Quote Link to comment
binhex Posted January 8, 2019 Author Share Posted January 8, 2019 13 hours ago, repomanz said: while unpacking; seems it does not honor cpu pinning. IE; even though i have cpu 1,5 pinned, it's maxing out all of my cpus. if you are really seeing this issue then its either a docker engine issue or an unraid issue, as pinning is done via the unraid web ui and sent to the docker engine, there is no additional processing within the container. 13 hours ago, repomanz said: Seeing above posts are there plans to fix unpacking issues? the fix is currently not known so no fix can be put in place, there has been a lot of back and forth with nzbget devs and nothing concrete came out of it. Im hoping the next release will not have this issue, but im not holding my breath. Quote Link to comment
iamthejoker Posted January 25, 2019 Share Posted January 25, 2019 Hello all, I just switched to using nzb recently and after reading this forum learned I should install v19 of nzbget due to a possible unpacking problem with v20 so I installed v19 as directed in the earlier posts and configured nzbget using spaceinvader ones video. Unfortunately nzbget is hanging at the unpacking stage. I downloaded a 1gb file and its been over 30mins now with no result. I am running a fx6300 and the /data folder is mapped to my cache drive which is an SSD. There has been no error message yet with the unpacking of the file its just stuck at the moment. I was reading on another forum about direct unpack, this option is off right now. Should I turn it on? Does that affect how sonarr post-processes? Any other hints about this problem? Quote Link to comment
JonathanM Posted January 25, 2019 Share Posted January 25, 2019 6 minutes ago, iamthejoker said: There has been no error message yet with the unpacking of the file its just stuck at the moment. Click on the nzbget docker icon and click restart on the popup menu, then check the status of the download. Quote Link to comment
iamthejoker Posted January 25, 2019 Share Posted January 25, 2019 20 minutes ago, jonathanm said: Click on the nzbget docker icon and click restart on the popup menu, then check the status of the download. Thanks! I actually had to stop the container then start again and it works perfect. Quote Link to comment
Recommended Posts
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.