bramabull Posted September 30, 2023 Share Posted September 30, 2023 Totally jumping on this test.. my repairs have been super slow and cpu intensive Quote Link to comment
nasbox Posted October 18, 2023 Share Posted October 18, 2023 (edited) Firstly, Binhex, I've been a long-time user of your docker repositories. Just awesome. Thank you.  For what it's wroth, I too am having unusual activity recently with sanznbdvpn, after a few downloads my unpacks become inexplicably slow, which coincides with downloads becoming slow - download speeds start 'yo-yoing'.  Thinking this may have been related to par2cmdline-turbo, I tried Binhex's updated docker image tagged 'test' which includes par2cmdline-turbo. To be fair, normal unpack speeds seem quicker, it seems to work. But I am still getting 'yo-yo' like download speeds which coincide with strangely slow unpacks. These occur after a bit of sustained downloading. At first I thought it was my ISP or VPN (PIA), but this wouldn't explain the slow unpacking. This was tested using both 1) a RAID1 BTRFS 2x SSD Cache, and 2) an XFS 1x SSD Cache. It doesn't seem to be related to storage write/read speeds.  I've also set direct_unpack_threads (Default 3) to 6, to give sabnzbd a bit more grunt - no joy (I'm running a 13500 with 20 threads + 32GB of Ram, which should be plenty).  Here is an example of the yo-yoing:   You can see that the speeds have gone from a locked 88MBps (where I cap it, I have a 1Gbps connection), and started yo-yoing. This behaviour coincided with an unpack process slowing down (pictured below). Pausing the downloads, letting the unpacks finish and restarting fixes the issue, albeit temporarily:   After a while, the yo-yoing behaviour starts again. Interestingly, the time it takes for yo-yoing to start varies. You can see below that downloads held constant at 88MBps until the strange unpacking/download speed behaviour started again.   I thought I'd share my experience as this seems to be impacting more and more people.  My motherboard has a Dragon 2.5G LAN + Intel® Gigabit LAN, the same behaviour occurs on both.  Hope this post helps.  EDIT1: I should say I'm new to Unraid (Jan of this year), but have been using Binhex's repositories on Synology NAS systems for years. Also, Unraid team - you are amazing. An absolutely great platform - thanks to you too! Edited October 18, 2023 by nasbox Quote Link to comment
binhex Posted October 19, 2023 Author Share Posted October 19, 2023 15 hours ago, nasbox said: Pausing the downloads, letting the unpacks finish and restarting fixes the issue, albeit temporarily: If the yo-yo speeds happen when unpacking or par running andthe yo-yo stops when you pause the unpack/par then it most probably is IO or CPU related, check your CPU and IO usage next time it happens, you could also try downloading and unpacking to different locations, so download to SSD and unpack directly to the array for instance, or even to RAM if you have enough. Quote Link to comment
nasbox Posted October 20, 2023 Share Posted October 20, 2023 10 hours ago, binhex said: If the yo-yo speeds happen when unpacking or par running andthe yo-yo stops when you pause the unpack/par then it most probably is IO or CPU related, check your CPU and IO usage next time it happens, you could also try downloading and unpacking to different locations, so download to SSD and unpack directly to the array for instance, or even to RAM if you have enough.  Thanks for the prompt response.  Overnight, I decided to test whether FUSE was causing the issue. I remapped /mnt/user/downloads to /mnt/cache_patriot/downloads - no joy. Not FUSE related.  After reading your response I remapped downloads & unpacking (.../usenet/incomplete & .../usenet/complete) to RAM (via Unraid's /tmp/... folder). My logic: I wanted to identify whether it was a CPU problem (which I doubted) or IO issue (which, admittedly, I also doubted) - problem solved! Downloading, unpacking and or repairing in RAM resolved the yo-yo problem.  I have to admit I was surprised, my current Cache Pool arrangements is:   Cache_nvme: 2x Raid1 NVME: For Docker, VMs, etc Cache_patriot: 1x Cheap Patriot SSD: For downloads, transcoding, and anything with high IO Cache_ssd: 2x Raid1 SSD: general Cache for data requiring redundancy  The yo-yo occurred on both the patriot & raid1-ssd cache pools. It didn't occur straight away, for between 20m and ~1h of sustained 88MBs downloading, SabNZB was fine downloading and unpacking files. Randomly, it would start, and occur regularly, not going away until a restart. After the restart, the cycle would start again. This pattern of behaviour made me think it was a strange i) Unraid issue, ii) Sabnzb issue, and or iii) a combination of both. This thinking was compounded by the problem having only started occurring in the last ~2-3 months (it ran fine on the cache_ssd pool for a long time, when I first setup Unraid).  I'd love to continue downloading to RAM. But my server lives in a Jonsbo N3 which requires an mITX mobo, max RAM at this stage is 64G. This isn't sufficient for large nzb files.  I have moved my downloads folder to the nvme Cache Pool which works fine (just like RAM). This is probably not an ideal long term solution as the high IO is using up 2x NVMEs - the whole point of the Patriot SSD was to avoid this.  I may have to find a good SSD which can deal with the IO.  Thanks for your help. Excuse the length of this post, I wanted to share in the hope it helps others. This was driving me crazy!  PS. If anyone can recommend an SSD which works well with SabNZB, please shout out.  Quote Link to comment
binhex Posted October 20, 2023 Author Share Posted October 20, 2023 6 hours ago, nasbox said: The yo-yo occurred on both the patriot & raid1-ssd cache pools. It didn't occur straight away, for between 20m and ~1h of sustained 88MBs downloading, SabNZB was fine downloading and unpacking files. Randomly, it would start, and occur regularly, not going away until a restart. I would suspect when the machine is freshly booted then the Patriot SSD has a clean cache (onboard of the SSD) and as you use the SSD more the cache fills up causing read/writes to slow down, I mean it could be a firmware bug for the Patriot SSD, worth investigating if there is an update available, failing that ditch that sucker an get yourself something a little faster - the Samsung Evo series are always solid, I have an Evo 850 that has been going strong as my download drive for literally years!, then i use a Samsung 970 Po for Docker image, VM's and appdata - I cannot guarantee it will work for your specific use case, but it should. 1 Quote Link to comment
nasbox Posted October 22, 2023 Share Posted October 22, 2023 On 10/20/2023 at 7:19 PM, binhex said: I would suspect when the machine is freshly booted then the Patriot SSD has a clean cache (onboard of the SSD) and as you use the SSD more the cache fills up causing read/writes to slow down, I mean it could be a firmware bug for the Patriot SSD, worth investigating if there is an update available, failing that ditch that sucker an get yourself something a little faster - the Samsung Evo series are always solid, I have an Evo 850 that has been going strong as my download drive for literally years!, then i use a Samsung 970 Po for Docker image, VM's and appdata - I cannot guarantee it will work for your specific use case, but it should.  Thanks for the response - I took your recommendation and bought a Samsung EVO 870 500g HD for my downloads - works perfectly. I didn't realise how different SSDs could be.  I also reconsidered how SABnzb downloads, I've set the incomplete directory to the new Evo SSD to minimise IO, and the complete directory to the Cache Pool (where movies go). This minimises IO while allowing Sonarr/Radarr to use Hardlinks when moving files to the media library.  Thanks again for your help, and SSD recommendation - all works perfectly now. 1 Quote Link to comment
eb98jdb Posted November 1, 2023 Share Posted November 1, 2023 Pretty sure I've tweaked something in my settings somewhere regarding how sabnzbd is writing to the array. Originally I was saturating my gigabit internet - now hitting only 85 Mbps. Have tested on another device with same settings on sabnzbd and it hits the limit.  downloads are set to hit Cache medis pool set to hit Cache then Array.  What have I set wrong? Quote Link to comment
nasbox Posted November 5, 2023 Share Posted November 5, 2023 On 11/2/2023 at 3:24 AM, eb98jdb said: Pretty sure I've tweaked something in my settings somewhere regarding how sabnzbd is writing to the array. Originally I was saturating my gigabit internet - now hitting only 85 Mbps. Have tested on another device with same settings on sabnzbd and it hits the limit.  downloads are set to hit Cache medis pool set to hit Cache then Array.  What have I set wrong?  If you think you're write speeds are slow due to downloading to the Array (ie. IO speeds), check if this is the case by changing the download/incomplete & download/complete folder to RAM. You can do this by mapping these folders to either /shm (a folder which gives you access to 50% of RAM), or /tmp (all of RAM). In doing so, you should make sure that you have ample RAM to download your test file without maxing out RAM (that would be bad). If this downloads at max speed, then it's likely an IO issue. I used this method to prove my slow write speeds were IO.  I never download to the Array, for me it's full of HDDs, which are much slower than SSD. Plus, if you have a Parity drive, you're just wasting IO. Setup a Cache drive with an SSD and download to that. I've recently moved to a Samsung EVO, which works nicely for me.  Added point: If you're using the Binhex VPN containers, I have found in the past that the DNS name servers I was using were very slow. Slow DNS servers resulted in slow download speeds. As the DNS servers were intermittently slow, the slow download speeds were also intermitent, making diagnosing this problem hard. I changed the standard name servers to PIA's DNS server (I use PIA as my VPN). If you don't use PIA, you could try Cloudflare's or Google's DNSs.  Good Luck. Quote Link to comment
K1LLA_KING_KING Posted November 12, 2023 Share Posted November 12, 2023 (edited) My Sab is not downloading anything all of a sudden: Indexers are working fine (and active) and can grab: this is a test download of a file which i had already succesfully downloaded previously, just to prove it was available. Some will start but always show missing articles, and thats for anything. It suggests to me the problem is with newshosting.com  NZB server is newshosting.com which is active and tests good: logs: more testing now suggests a sab problem: sab test DL failed Edited November 12, 2023 by K1LLA_KING_KING Quote Link to comment
jonesc Posted December 7, 2023 Share Posted December 7, 2023 Has there been any changes to changing the path for downloads?  I changed the data path to use /data/mnt/user/downloads/sabnzbd/ but for some reason cannot browse anything inside even with RW permission.  Sounds like im missing something simple, using similar method has worked for Sonarr. Quote Link to comment
Rex099 Posted December 21, 2023 Share Posted December 21, 2023 On 9/28/2023 at 4:54 AM, binhex said: ive added this to a 'test' tagged image, please pull down, if you dont know how to specify the 'test' tag then see Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md Will this ever be rolled into the latest tag? Quote Link to comment
binhex Posted December 21, 2023 Author Share Posted December 21, 2023 30 minutes ago, Rex099 said: Will this ever be rolled into the latest tag? it was pushed to main, is this not present in the latest tagged image? Quote Link to comment
Rex099 Posted December 22, 2023 Share Posted December 22, 2023 22 hours ago, binhex said: it was pushed to main, is this not present in the latest tagged image? If i load binhex/arch-sabnzbd it shows "Par2cmdline-turbo:Not available" but if I load binhex/arch-sabnzbd:test it shows its working Quote Link to comment
Schokobecher Posted December 23, 2023 Share Posted December 23, 2023 (edited) Can confirm this on a fresh install, I had to manually install it using aur.sh  Maybe there's an issue with the TARGETARCH? If it returns arm64 it skips the aur_packages Edited December 23, 2023 by Schokobecher Added more insight Quote Link to comment
Globe89 Posted December 25, 2023 Share Posted December 25, 2023 (edited) I'm having an issue with sabnzbd sending SMTP messages to my local mail server (10.13.2.220) I configured VPN_OUTPUT_PORTS=25, which is the port for my SMTP server. But test emails are failing to be sent with the VPN up.  sabnzbdvpn: image: binhex/arch-sabnzbdvpn:4.0.3-1-03 container_name: sabnzbdvpn privileged: true environment: - VPN_ENABLED=yes - VPN_PROV=protonvpn - VPN_CLIENT=wireguard - STRICT_PORT_FORWARD=no - ENABLE_PRIVOXY=yes - LAN_NETWORK=10.13.2.1/24,10.189.177.0/24 - NAME_SERVERS=1.1.1.1 - VPN_INPUT_PORTS=50005 - VPN_OUTPUT_PORTS=25 - DEBUG=true - UMASK=000 - PUID=0 - PGID=0 volumes: - /mnt/data/:/data - /apps/docker/sabnzbd/config:/config - /etc/localtime:/etc/localtime:ro ports: - 8080:8080 - 8090:8090 - 8119:8118 restart: unless-stopped  Edited December 25, 2023 by Globe89 Quote Link to comment
Slin Posted January 16 Share Posted January 16 Can someone help me understand the paths I need to enter to get SabNZB working with Radarr, Sonarr and Plex I have created a share called media, within that, two folders Films and TV. I want films ans Tv series automaticaly placed in those folders when the have been downloaded. Quote Link to comment
jeff.lebowski Posted January 17 Share Posted January 17 5 hours ago, Slin said: Can someone help me understand the paths I need to enter to get SabNZB working with Radarr, Sonarr and Plex I have created a share called media, within that, two folders Films and TV. I want films ans Tv series automaticaly placed in those folders when the have been downloaded.  Your download path should be to a cache disk, so: /mnt/cache/Downloads/sonarr/ The Container path should be default: /data  Your media paths should be /mnt/Media/TV and /mnt/Media/Films The container path should also be default: /media Quote Link to comment
dgwharrison Posted April 14 Share Posted April 14 Hi @binhex, thanks again for all the amazing containers.  My Sonarr container seems to have died, i had a look at the logs and i think maybe failed to upgrade a database or something. What’s the safest way of fixing this problem? Just would rather avoid a complete rebuild.  Logs: https://pastebin.com/RG6xpQs7 Quote Link to comment
Teffi71 Posted April 25 Share Posted April 25 (edited) SOLVED: I needed to delete all cookies for the Docker IP of SABnzbd. After that, I was able to log in again! Â Â Today, I wanted to check on SABnzbd and was greeted by this error message: Â Is this issue already reported and known? Thanks, Stefan Edited April 25 by Teffi71 Found the solution to my problem! Quote Link to comment
Teffi71 Posted April 25 Share Posted April 25 ... and the log: Â text error warn system array login 2024-04-25 12:01:55,852 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,852::INFO::[__init__:323] All processes started 2024-04-25 12:01:55,852 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,852::INFO::[SABnzbd:338] Template location for Glitter is /usr/lib/sabnzbd/interfaces/Glitter 2024-04-25 12:01:55,852 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,852::INFO::[SABnzbd:338] Template location for Config is /usr/lib/sabnzbd/interfaces/Config 2024-04-25 12:01:55,852 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,852::INFO::[misc:1230] [N/A] Running external command: ['/usr/sbin/unrar'] 2024-04-25 12:01:55,854 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,854::INFO::[misc:1230] [N/A] Running external command: ['/usr/sbin/7za'] 2024-04-25 12:01:55,857 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,857::INFO::[misc:1230] [N/A] Running external command: ['/usr/sbin/par2', '-V'] 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:423] SABCTools module (v8.1.0)... found! 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:424] SABCTools module is using SIMD set: AVX2 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:425] SABCTools module is linked to OpenSSL: True 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:445] Cryptography module (v41.0.7)... found! 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:451] par2 binary... found (/usr/sbin/par2) 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:458] UNRAR binary... found (/usr/sbin/unrar) 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:466] UNRAR binary version 7.00 2024-04-25 12:01:55,858 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:473] 7za binary... found (/usr/sbin/7za) 2024-04-25 12:01:55,859 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,858::INFO::[SABnzbd:475] 7za binary version 17.05 2024-04-25 12:01:55,859 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,859::INFO::[SABnzbd:481] nice binary... found (/usr/sbin/nice) 2024-04-25 12:01:55,859 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,859::INFO::[SABnzbd:485] ionice binary... found (/usr/sbin/ionice) 2024-04-25 12:01:55,859 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,859::INFO::[SABnzbd:1270] HTTPS keys are OK 2024-04-25 12:01:55,860 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,860::INFO::[SABnzbd:1399] Starting web-interface on 0.0.0.0:8090 2024-04-25 12:01:55,860 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,860::INFO::[_cplogging:213] [25/Apr/2024:12:01:55] ENGINE Bus STARTING 2024-04-25 12:01:55,968 DEBG 'start-script' stdout output: 2024-04-25 12:01:55,967::INFO::[_cplogging:213] [25/Apr/2024:12:01:55] ENGINE Serving on https://0.0.0.0:8090 2024-04-25 12:01:56,070 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,070::INFO::[_cplogging:213] [25/Apr/2024:12:01:56] ENGINE Serving on http://0.0.0.0:8080 2024-04-25 12:01:56,071 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,070::INFO::[_cplogging:213] [25/Apr/2024:12:01:56] ENGINE Bus STARTED 2024-04-25 12:01:56,072 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,071::INFO::[SABnzbd:1444] Starting SABnzbd.py-4.2.3 2024-04-25 12:01:56,076 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,075::INFO::[dirscanner:111] Dirscanner starting up 2024-04-25 12:01:56,076 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,076::INFO::[panic:239] Launching browser with https://127.0.0.1:8090/sabnzbd 2024-04-25 12:01:56,078 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,077::INFO::[notifier:142] Sending notification: SABnzbd - SABnzbd 4.2.3 started (type=startup, job_cat=None) 2024-04-25 12:01:56,078 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,078::INFO::[zconfig:61] No bonjour/zeroconf support installed 2024-04-25 12:01:56,080 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,079::INFO::[ssdp:108] Serving SSDP on 172.17.0.2 as SABnzbd 2024-04-25 12:01:56,086 DEBG 'start-script' stdout output: 2024-04-25 12:01:56,086::INFO::[database:576] Scheduled history purge Looks ok to me ... Quote Link to comment
Teffi71 Posted April 25 Share Posted April 25 Adding on to my previous two posts: API calls continue to work local web access does not work What should I edit/delete within the docker to reset access control? TIA! P.S.: restoring a previous backup from appdata backup plugin did not resolve my local access issue ... Â Quote Link to comment
Teffi71 Posted April 25 Share Posted April 25 (edited) I was using Safari on my MBP and access was denied! I just tried Google Chrome and I do have access! Â Weird! Edited April 25 by Teffi71 typo correction Quote Link to comment
ich777 Posted April 25 Share Posted April 25 6 hours ago, Teffi71 said: Today, I wanted to check on SABnzbd and was greeted by this error message: This is caused because you have the WebUI from TVHeadend on the same IP running as SABnzbd. You have two (or maybe more) options: Make sure that TVHeadend and SABnzbd are not running on the same IP address Don't open the WebUI from TVHeadend and SABnzbd on the machine where you manly access the WebUI from SABnzbd (Open TVHeadend in a Private Browser window) (Open TVHeadend in another Browser that you don't user for SABnzbd) ... This is nothing weird this is a known issue. 1 Quote Link to comment
rabidfibersquirrel Posted May 28 Share Posted May 28 I suddenly can only download with Sab in short spurts before it instantly stops for a few minutes at time. The error in the log is as follows:  2024-05-28 13:50:54,087 DEBG 'start-script' stdout output: 2024-05-28 13:50:54,087::INFO::[_cplogging:213] [28/May/2024:13:50:54] ENGINE Client ('172.17.0.1', 59580) lost — peer dropped the TLS connection suddenly, during handshake: (1, '[SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1000)')  I'd like to understand what is happening and brainstorm some ideas on how to fix it. This began occurring suddenly after several months of issue-free downloading. Quote Link to comment
Flixlover Posted August 8 Share Posted August 8 Hello,  I have reset my server and reinstalled the sabnzbd and it gave me an error message "execution error, server error" How can I fix this? 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.