omkar Posted February 26, 2010 Share Posted February 26, 2010 Can someone list out the steps needed to configure SABnzbd to use SSL? I installed the dependencies package which includes SSL. I see the HTTPS choice under the General Settings. I'm not sure what to use for the HTTPS Certificate and Key. Quote Link to comment
KentBrockman Posted February 26, 2010 Share Posted February 26, 2010 I'm connected using SSL but I did not need to enable HTTPS. Are you sure it's required for SSL? Cheers Quote Link to comment
Orbi Posted February 26, 2010 Share Posted February 26, 2010 I'm connected using SSL but I did not need to enable HTTPS. Are you sure it's required for SSL? Cheers HTTPS is needed for remote access & control to Sabnzbd. It's not needed for an SSL connection with your newsserver. Quote Link to comment
omkar Posted February 26, 2010 Share Posted February 26, 2010 Sorry for the confusion. Yes, I am able to connect to my news server via SSL without any issues. I was hoping to control SABnzbd+ remotely using HTTPS. Quote Link to comment
gswarriorfan Posted March 12, 2010 Share Posted March 12, 2010 Is anyone able to control SABnzbd remotely here? I'd like to have the ability of switching up my queue while I'm at the office. Quote Link to comment
BRiT Posted March 12, 2010 Share Posted March 12, 2010 You mean by browsing to the SABnzbd web control page? Quote Link to comment
ClunkClunk Posted March 13, 2010 Share Posted March 13, 2010 I control SABnzbd remotely by forwarding SAB's port from my router to my unRAID, and making sure it's password protected (I also use dynamic DNS for a hostname). I use myNZB mostly (iPhone app), but I also connect to it via SABnzbdX and the standard web page as well. Quote Link to comment
gswarriorfan Posted March 14, 2010 Share Posted March 14, 2010 Does anyone have issues with the par2 repairing? There are 2 things that happen: 1) It seems like sometimes sabnzbd gets hung up after repairing. In this case I will just manually unrar it. 2) Sometimes the repair starts, but then stops after renaming the files with the .1 extension. In this case I just double click the par2 and let it repair, and then manually unrar. Just wondering if anyone else has these issues, and if they've been addressed. Quote Link to comment
BRiT Posted March 14, 2010 Share Posted March 14, 2010 I'm running a full install of SABnzbd on Slackware-Current and have never had the issues you posted. Quote Link to comment
gswarriorfan Posted March 14, 2010 Share Posted March 14, 2010 I'm running a full install of SABnzbd on Slackware-Current and have never had the issues you posted. Hmmm...interesting. This may become my next project for my unRAID server. How much space does it take up on the flash drive? I hope my 2gb flash is large enough. Did you follow the guidance on this forum post: http://lime-technology.com/forum/index.php?topic=2073.0 ? Quote Link to comment
BRiT Posted March 14, 2010 Share Posted March 14, 2010 I installed Slackware onto a hard-drive (cache drive). I followed those instructions, which are given with further details in the wiki [ http://lime-technology.com/wiki/index.php?title=Installing_unRAID_on_a_full_Slackware_distro ] combined with the ones from here [ http://lime-technology.com/forum/index.php?topic=3899.0 ] for partitioning info. Where I cut the steps short was in only copying/modifying 'rc.samba' and 'rc.local'. I prefer to use the standard Slackware/*nix management tools to control time sync (NNTP), and the 'rc.ifplugd' / 'ifplugd' is not needed at all if using 12.2 / 13.0 / 13.1 (Current). I even have unRAID running under the 64bit distro of Slackware-Current on my test virtual that uses the 2.6.33 kernel. The next time I build or have to rebuild my unRAID system, I'll go the 64bit route. The full slackware install uses around 4 - 5 Gigs. Quote Link to comment
gswarriorfan Posted March 15, 2010 Share Posted March 15, 2010 Awesome! Thanks! Is there any advantage for 64bit? Quote Link to comment
BRiT Posted March 15, 2010 Share Posted March 15, 2010 The only difference would be a slight performance difference in memory access if you have 4 GB or more on the server that's frequently used. If you have 4GB or less, then 32bit makes more sense. If you don't run VMWare/VirtualBox then 32bit makes more sense. If you're not bleeding edge and willing to experiment with your data, then 32bit makes more sense. In addition to that, unRAID on 64bit Slackware is largely untested -- I only figured out how to get it running yesterday (Saturday). Quote Link to comment
gswarriorfan Posted March 16, 2010 Share Posted March 16, 2010 BRiT, are you able to access your SABnzbd remotely? Quote Link to comment
BRiT Posted March 16, 2010 Share Posted March 16, 2010 I am able to access it from within my LAN. I have not punched through any holes in the firewall to allow connections from the outside world for SABnzbd. IIt's been nine months to a year since I initially configured it so I don't exactly remember what settings I changed in the configuration, one may have been which IP address it binds to (localhost only or external ip). If you double-checked the config and have it bound to a non-localhost only ip, then I would double-check the firewall/router port-forwarding config. Quote Link to comment
jupilerman Posted March 17, 2010 Share Posted March 17, 2010 Does anyone have issues with the par2 repairing? There are 2 things that happen: 1) It seems like sometimes sabnzbd gets hung up after repairing. In this case I will just manually unrar it. 2) Sometimes the repair starts, but then stops after renaming the files with the .1 extension. In this case I just double click the par2 and let it repair, and then manually unrar. Just wondering if anyone else has these issues, and if they've been addressed. Yes, I sometimes experience the issue number 2. And I solve it manualy like you do. But could this be related to the space left ? Because my unRAID is running out of space. Next time it happens, i'll look for it. Quote Link to comment
MortenSchmidt Posted March 22, 2010 Share Posted March 22, 2010 I got sabnzbd 5.0 final kind of working using the dependencies 1.3 package. It starts fine and will happily download a few files before terminating unexpectedly. When it has terminated this way, It won't start up again untill I clear it's cache directory. If I clear the cache folder and move the remaining nzb files from the nzb-backup folder to the watched folder, it will run again an hour or two before terminating. By terminating I mean the python process ceases to exist. It will usuall complete the nzb-file where it stalled restarting as described, and it does not seem to be crashing during par-check or unpacking, it seems to happen while downloading the parts. I'm running on 512MB RAM with unmenu, powerdown, apcupsc, email-notify, and smarthistory addons. I'm still a bit linux-green, but I have checked the memory usage in TOP and it seems to report almost nothing free but about 100MB buffer (keeps fluctuating up and down). Is this caused by low memory? Anybody got an idea what else it could be ? Quote Link to comment
gbdesai Posted March 22, 2010 Share Posted March 22, 2010 Are you keeping cache on a hard drive or is it on the flash? I noticed that when I used the 0.5.0 all in one installer, it includes a line to run SABnzbd using the default sabnzbd.ini in the install directory vs. the sabnzbd.ini which I keep somewhere else. I manually ran the installer package from the go script (and on port 89). I noticed I had two SABnzbds running one on 88 and one on 89. Now the one on 89, regardless of where the set the paths it still wrote them to directories relative to the sabnzbd file (as evidenced in the paths highlighted near the top of the folder configuration tab... Just a thought... Quote Link to comment
Orbi Posted March 22, 2010 Share Posted March 22, 2010 I found 512MB Ram a bit challenging for SABnzbd and the related repair and extract. I had instability problems too, being unable to query Sabnzbd at times when it was just downloading. It would sometimes just get killed by unraid as the system was running out of memory and trying to save its ass basically. I added another 512MB and I never had problems since. Repairs and extract are like twice faster, the GUI is much more responsive and refreshes are almost instantaneous . gbdesai is making a good suggestion, but I also advice you to the RAM upgrade course. IMHO UnRaid + SABnzbd on 512MB ram is a not an ideal situation. Your server is at neck height under water. Quote Link to comment
MortenSchmidt Posted March 22, 2010 Share Posted March 22, 2010 I'm not using the all-in-one package, but rather the Dependencies. I find it better to start the python process myself with the "| at now + 1 minute" thing documented in this thread, that way I controll the location of the ini file (on my flash drive), and I can easily upgrade Sabnzbd versions if I want to try a newer one. OK, I had not anticipated the all-in-one package with 5.0 final coming out so shortly after it's release, either.. But Roger that on the memory advice. Studying the syslog I do see that kernel is killing off python on a low-memory event. Here is a snip: Mar 21 01:36:12 FileServer kernel: dd invoked oom-killer: gfp_mask=0x201d0, order=0, oomkilladj=0 Mar 21 01:36:12 FileServer kernel: Pid: 9598, comm: dd Not tainted 2.6.31.12-unRAID #1 Mar 21 01:36:12 FileServer kernel: Call Trace: Mar 21 01:36:12 FileServer kernel: [<c1047d7a>] oom_kill_process+0x5e/0x1ce Mar 21 01:36:12 FileServer kernel: [<c1048066>] ? badness+0x15a/0x191 Mar 21 01:36:12 FileServer kernel: [<c10480ce>] __out_of_memory+0x31/0x10c Mar 21 01:36:12 FileServer kernel: [<c1048207>] out_of_memory+0x5e/0x83 Mar 21 01:36:12 FileServer kernel: [<c104a0e2>] __alloc_pages_nodemask+0x380/0x43d Mar 21 01:36:12 FileServer kernel: [<c104bd1a>] __do_page_cache_readahead+0x8e/0x169 Mar 21 01:36:12 FileServer kernel: [<c104be0c>] ra_submit+0x17/0x1c Mar 21 01:36:12 FileServer kernel: [<c104c016>] ondemand_readahead+0x14e/0x15a Mar 21 01:36:12 FileServer kernel: [<c104c075>] page_cache_async_readahead+0x53/0x5e Mar 21 01:36:12 FileServer kernel: [<c1046f67>] generic_file_aio_read+0x24c/0x51a Mar 21 01:36:12 FileServer kernel: [<c1067ace>] do_sync_read+0xbb/0xf9 Mar 21 01:36:12 FileServer kernel: [<c10861b1>] ? block_ioctl+0x2c/0x34 Mar 21 01:36:12 FileServer kernel: [<c10326a5>] ? autoremove_wake_function+0x0/0x30 Mar 21 01:36:12 FileServer kernel: [<c1067a13>] ? do_sync_read+0x0/0xf9 Mar 21 01:36:12 FileServer kernel: [<c1068146>] vfs_read+0x8a/0x114 Mar 21 01:36:12 FileServer kernel: [<c10684dd>] sys_read+0x3b/0x60 Mar 21 01:36:12 FileServer kernel: [<c1002975>] syscall_call+0x7/0xb Mar 21 01:36:12 FileServer kernel: Mem-Info: Mar 21 01:36:12 FileServer kernel: DMA per-cpu: Mar 21 01:36:12 FileServer kernel: CPU 0: hi: 0, btch: 1 usd: 0 Mar 21 01:36:12 FileServer kernel: Normal per-cpu: Mar 21 01:36:12 FileServer kernel: CPU 0: hi: 186, btch: 31 usd: 182 Mar 21 01:36:12 FileServer kernel: Active_anon:23887 active_file:191 inactive_anon:22433 Mar 21 01:36:12 FileServer kernel: inactive_file:94 unevictable:67784 dirty:4 writeback:10 unstable:0 Mar 21 01:36:12 FileServer kernel: free:1221 slab:4388 mapped:2538 pagetables:328 bounce:0 Mar 21 01:36:12 FileServer kernel: DMA free:2068kB min:84kB low:104kB high:124kB active_anon:9452kB inactive_anon:3316kB active_file:32kB inactive_file:0kB unevictable:12kB present:15804kB pages_scanned:0 all_unreclaimable? no Mar 21 01:36:12 FileServer kernel: lowmem_reserve[]: 0 491 491 491 Mar 21 01:36:12 FileServer kernel: Normal free:2816kB min:2792kB low:3488kB high:4188kB active_anon:86096kB inactive_anon:86416kB active_file:732kB inactive_file:376kB unevictable:271124kB present:503172kB pages_scanned:950 all_unreclaimable? no Mar 21 01:36:12 FileServer kernel: lowmem_reserve[]: 0 0 0 0 Mar 21 01:36:12 FileServer kernel: DMA: 517*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2068kB Mar 21 01:36:12 FileServer kernel: Normal: 704*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2816kB Mar 21 01:36:12 FileServer kernel: 68128 total pagecache pages Mar 21 01:36:12 FileServer kernel: 0 pages in swap cache Mar 21 01:36:12 FileServer kernel: Swap cache stats: add 0, delete 0, find 0/0 Mar 21 01:36:12 FileServer kernel: Free swap = 0kB Mar 21 01:36:12 FileServer kernel: Total swap = 0kB Mar 21 01:36:12 FileServer kernel: 130864 pages RAM Mar 21 01:36:12 FileServer kernel: 0 pages HighMem Mar 21 01:36:12 FileServer kernel: 2299 pages reserved Mar 21 01:36:12 FileServer kernel: 11252 pages shared Mar 21 01:36:12 FileServer kernel: 123928 pages non-shared Mar 21 01:36:12 FileServer kernel: Out of memory: kill process 6127 (python) score 5476 or a child Mar 21 01:36:12 FileServer kernel: Killed process 6127 (python) Can someone help me get a good overview of the memory consumption of each process, because I am obviously not reading the TOP command output correctly. I am using this box with 512MB as a temporary solution the next couple of months - I might be able to do without some of my other addons, I just would like to see how much each takes. Quote Link to comment
MortenSchmidt Posted March 23, 2010 Share Posted March 23, 2010 OK, think I see the problem now. Still don't know how to see how much mem the other addons take, but I just noticed the Python process goes from 10-12% Memory up to ~25% in TOP when I add my nzb files to the queue. We are talking 21 nzb files added after 3 existing ones, that is all. Sabnzbd wat already downloading the first of 3 queued files, and adding 21 more to the queue doubles the memory consumption (!). That does seem an inefficient use of memory and explains why sabnzbd was working for me when just testing it out with one nzb file. So, I guess I will be OK as long as I just queue up very few files at a time, but if this is the quality of the programming in this app, I might be temptet to checkout getnzb instead. Quote Link to comment
daldridge Posted April 2, 2010 Share Posted April 2, 2010 Does anyone have issues with the par2 repairing? There are 2 things that happen: 1) It seems like sometimes sabnzbd gets hung up after repairing. In this case I will just manually unrar it. 2) Sometimes the repair starts, but then stops after renaming the files with the .1 extension. In this case I just double click the par2 and let it repair, and then manually unrar. Just wondering if anyone else has these issues, and if they've been addressed. I was having these issues also, fortunately I found a fix that works for me... unfortunately the repair seems to take a little bit longer than what it used to. I've found that replacing the par2 executable with the one from here: http://code.google.com/p/unraid-weebotech/downloads/list seems to fix the issue. Like always, YMMV. Quote Link to comment
CaptainSpalding Posted April 6, 2010 Share Posted April 6, 2010 First off, thank you for this nice software and especially for the all-in-one package! Now for the question, How can I change the folder path that seems to be fixed? In "/boot/custom/usr/share/packages/sabnzbd" I cannot change that through the webGUI. EDIT: SOLVED with the earlier posts. Quote Link to comment
markro1 Posted April 6, 2010 Share Posted April 6, 2010 This worked like gangbusters for me! I love it. I just downloaded the All in One package Romir posted on Page 4 http://www.bibliognome.com/unraid/SABnzbd-0.5.0-i586-unRAID.tgz Copied it to the dir on the flash Added this to my Go Script # SABnzbd Install cd /boot/custom/usr/share/packages/SABnzbd/ installpkg *.tgz python SABnzbd.py -d -f /boot/custom/SABnzbd/SABnzbd.ini And then opened up http://tower:88 and it was done. Awesome Job folks. Quote Link to comment
CaptainSpalding Posted April 8, 2010 Share Posted April 8, 2010 I'm having a weird problem. Sabnzb is downloading to two hdd's at the same time and those won't show in "My Network Places" in Windows. The program and download folders are on one of those drives, so maybe for that reason I cannot access to Sabnzb. All hdd's have green dots in Main. What could cause 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.