Install SABnzbd+ on Netgear ReadyNas Duo

[thibs]

I wrote a full tutorial to install SABnzbd+ on a ReadyNas Duo :
http://www.thibernet.com/442-install-sa ... adynas-duo

Have fun ;-)

[shypike]

Cool, I'll put a link in our "installing" Wiki page.
Thanks.

[sander]

Cool indeed!

Talking about the Wiki, SABnzbd installation and NAS-devices:

http://sabnzbd.wikidot.com/install-other mentions the Buffalo Linkstation and the NetGear ReadyNas Duo
http://sabnzbd.wikidot.com/install-unix mentions the Synology DS107e

Mabye installation on NAS devices deserves it own's page (something like http://sabnzbd.wikidot.com/install-nas), with these devices mentioned.

And I believe SAB can also be installed on the:

Conceptronic CH3SNAS / Dlink DNS-323. See old, Dutch instruction here: http://gathering.tweakers.net/forum/lis ... 2#29376532
QNAP, see http://forums.sabnzbd.org/index.php?topic=770.0

[johnyb]

Thanks for the guide, but could use some help. Go this far and got error..

ReadyNas:~/src# dpkg-deb -x coreutils_5.2.1-2_sparc.deb ../usr/bin/uniq –version # should work
dpkg-deb: –extract takes at most two arguments (.deb and directory)

Type dpkg-deb –help for help about manipulating *.deb files;
Type dpkg –help for help about installing and deinstalling packages.
ReadyNas:~/src# dpkg-deb -x coreutils_5.2.1-2_sparc.deb ../usr/bin/uniq
dpkg-deb: failed to create directory: No such file or directory
ReadyNas:~/src# dpkg-deb -x coreutils_5.2.1-2_sparc.deb ./usr/bin/uniq
dpkg-deb: failed to chdir to directory: Not a directory
ReadyNas:~/src# dpkg-deb -x coreutils_5.2.1-2_sparc.deb ../usr/bin/uniq –version
dpkg-deb: –extract takes at most two arguments (.deb and directory)

Type dpkg-deb –help for help about manipulating *.deb files;
Type dpkg –help for help about installing and deinstalling packages.

[sander]

ReadyNas:~/src# dpkg-deb -x coreutils_5.2.1-2_sparc.deb ../usr/bin/uniq –version # should work

I don't know which information you're using, but ... that command does not look OK (as the error message tells too): it looks like two commands on one line: the part "dpkg-deb -x coreutils_5.2.1-2_sparc.deb " could be OK, but the part "../usr/bin/uniq –version # should work
" after that does not look like it should be there (at least not on that same line).

[johnyb]

My appologies, yuo are correct, it's two seperate lines... WHat a twat...

Anyway all the way through the guide, although downloaded and installled newer version of SABnzbd-0.4.11 (not 0.4.6).  Problem now is that when I attempt to run the app i get the following error....

ReadyNas:~# /etc/init.d/sabnzbd start
Starting SABnzbd.
/usr/local/bin/python2.5: can't open file '/usr/local/src/SABnzbd/SABnzbd.py': [Errno 2] No such file or directory
ReadyNas:~#

So python is installed ok, but cannot seem to find where SABnzbd has installed.... neither the /user/local/src/SABnzbd folder nor the /etc/SABnzbd/
Any ideas?

Also no where within the instructions did we create /etc/SABnzbd/sabnzbd.ini ?


UPDATE:- so found the locations of the SABnzbd.py file and manualy ran the following: /usr/local/bin/python2.5 /root/src/SABnzbd-0.4.11/SABnzbd.py
This fires up but since no SABnzbd.ini files uses it own defaults (eg port 8080), but the interface is not accessable..

[johnyb]

I really would appreciate some help with installing this program, could anyone check out the script and see where the problem is? Thanks

[mrchris76]

Hi all, has anyone managed to get the 0.5.0 beta running on their Duo? I have problems with the pysqlite version required.

Code: Select all

ReadyNAS:~/src/SABnzbd-0.5.0Beta3# python SABnzbd.py
Sorry, requires Python module sqlite3 (pysqlite2 in python2.4)
Try: apt-get install python-pysqlite2

Its not available in the repos..

Cheers

[chinchin]

Hi mrchris, I had the same issue but have now resolved it with the BETAs. I just installed Beta 5 and it worked fine, although I do have other issues but these are unrelated to the installation.

For all the ReadyNAS NV+ users out there here are some complete step by step installation notes. Please let me know if you have any problems and I'll do my best to help but I'm no expert and that Python sqlite was a real pain to solve. I used the original install notes given as my foundation and built the following. Anyway take a look and lets see what questions I get :D

Installation and Configuration of ReadyNAS  NV+


========================================================
Setup Dns-o-matic

  1. Install Root Access via ToggleSSH and EnableRootSSH

In ReadyNAS NV Admin > System > Update > Local Tab

      Upload the bin files there.

  2. Download and install DnsOMatic add-on

http://www.readynas.com/forum/viewtopic ... 47&t=28347

  3. In ReadyNAS NV Admin > Services > Installed Add-ons > Disable DnsOMatic add on
  4. Winscp/Putty with Root user to /c/addons-scripts/DnsOMatic open dnsomatic file and insert Username/Password

Setup SABnzbd

(http://www.thibernet.com/442-install-sa ... adynas-duo)

  1. Install Add on APT-GET
  2. Putty root access to NAS
  3. Run:
        1. apt-get update
        2. apt-get install libc6-dev
        3. apt-get install gcc
        4. apt-get install gdb
        5. apt-get install libtag1-dev
        6. apt-get install uuid-dev
  4. mkdir /root/src
  5. cd /root/src
  6. Run:
        1. apt-get install unrar unzip
        2. apt-get install par2 parchive
        3. apt-get install gpp
        4. apt-get install libssl-dev
        5. apt-get install zlibc
        6. apt-get install zlib1g-dev
  7. Install Python 2.5
        1. wget http://www.python.org/ftp/python/2.5.4/Python-2.5.4.tgz
        2. gzip –d Python-2.5.4.tgz
        3. tar xf Python-2.5.4.tar
        4. cd Python-2.5.4
        5. ./configure –build=sparc-linux
        6. make
        7. make install
        8. cd ..
  8. Install pysqlite
        1. wget http://pysqlite.googlecode.com/files/py ... 5.6.tar.gz
        2. gzip -d pysqlite-2.5.6.tar.gz
        3. tar xf pysqlite-2.5.6.tar
        4. cd pysqlite-2.5.6
        5. python setup.py build_static install
        6. Configure Python to have an alias for sqlite3
              1. python
              2. from pysqlite2 import dbapi2 as sqlite3
              3. exit()
  9. Install Cheetah 2.0.1
        1. wget http://mesh.dl.sourceforge.net/sourcefo ... 0.1.tar.gz
        2. gzip –d Cheetah-2.0.1.tar.gz
        3. tar xf Cheetah-2.0.1.tar
        4. cd Cheetah-2.0.1
        5. python2.5 setup.py install
        6. cd ..
  10. Install yenc
        1. wget http://sabnzbd.sourceforge.net/yenc-0.3.tar.gz
        2. gzip –d yenc-0.3.tar.gz
        3. tar xf yenc-0.3.tar
        4. cd yenc-0.3
        5. python2.5 setup.py install
        6. cd ..
  11. Install feedparser
        1. wget http://feedparser.googlecode.com/files/ ... er-4.1.zip
        2. mkdir feedparser-4.1
        3. cd feedparser-4.1
        4. unzip ../feedparser-4.1.zip
        5. python2.5 setup.py install
        6. cd ..
  12. Install pyOpenSSL-0.9
        1. wget http://garr.dl.sourceforge.net/sourcefo ... 0.9.tar.gz
        2. tar xvzf pyOpenSSL-0.9.gz
        3. cd pyOpenSSL-0.9
        4. python2.5 setup.py install
        5. cd ..
  13. Install SABnzbd 0.5.0 Beta 4
        1. wget http://downloads.sourceforge.net/projec ... irror=garr
        2. gzip –d SABnzbd-0.5.0Beta4a-src.tar.gz
        3. tar xf SABnzbd-0.5.0Beta4a-src.tar
        4. cd SABnzbd-0.5.0
        5. python2.5 –OO SABnzbd.py -v
            If everything has installed correctly that should produce a normal output with some nonchalant statements about versions etc.
( 14. Or try SABnzbd 0.5.0 Beta 5

  1. wget http://downloads.sourceforge.net/projec ... or=surfnet
?)

Create a file /etc/init.d/sabnzbd :
#!/bin/sh
case "$1" in
start)
  echo "Starting SABnzbd."
  /usr/local/bin/python2.5 /root/src/SABnzbd-0.5.0Beta4/SABnzbd.py -d -f /etc/SABnzbd/sabnzbd.ini
;;
stop)
  echo "Shutting down SABnzbd."
  /usr/bin/wget -q --delete-after "http://192.168.0.50:7777/sabnzbd/api?mode=shutdown"
;;
*)
  echo "Usage: $0 {start|stop}"
  exit 1
esac
exit 0


Add it on startup:
cd /etc/rc3.d/
ln -s /etc/init.d/sabnzbd S05sabnzbd

Try cd /etc/init.d/
chmod +x sabnzbd
./sabnzbd start


When that is completed go to /etc/SABnzbd/log and you will see the folder has now been created along with the config file in /etc/SABnzbd. In the sabnzbd.ini file you will see a marker host, remove localhost and enter the ip address of the NAS - Please reserve this address in your router so that it always receives the same IP. Now check the config webpage has been started correctly under:

http://192.168.0.50:8080

========================================================

[snapper]

chinchin,

Great instructions, when I followed them exactly I managed to get everything to install - but I can't get sabnzbd to actually start on my NV

I didn't install DNSoMatic - as I couldn't  see why I need that - my external IP is registered to Dynds by my DD-Wrt router - if there's a compelling reason for using thiplease let me know.

I installed the fisrt time using Beta 5, and got to the configuration wizard, and configured sabnzbd the same way I have it running locally on my Mac. When I go to restart sabnzbd on the NV, and configure it, I can't get it to start. More accurately, it starts then shuts down as the ports it want to use are being used alread - according to sabnzbd, though using netstat I can' see those ports being used by anything else..

I've atached a log excerpt here:

Code: Select all

bigdisk:/etc/SABnzbd/logs# tail -60 *d.log
2010-01-06 23:04:51,903::INFO::[SABnzbd:394] unrar binary... found (/usr/bin/unrar)
2010-01-06 23:04:51,909::INFO::[SABnzbd:399] unzip binary... found (/usr/bin/unzip)
2010-01-06 23:04:51,916::INFO::[SABnzbd:405] nice binary... found (/usr/bin/nice)
2010-01-06 23:04:51,923::INFO::[SABnzbd:411] ionice binary... NOT found!
2010-01-06 23:04:51,929::INFO::[SABnzbd:414] pyOpenSSL... found (True)
2010-01-06 23:04:51,968::INFO::[SABnzbd:1101] Starting web-interface on 192.168.0.11:8080
2010-01-06 23:04:51,980::INFO::[_cplogging:55] [06/Jan/2010:23:04:51] ENGINE Bus STARTING
2010-01-06 23:04:51,945::INFO::[__init__:637] Saving data for watched_data.sab in /etc/SABnzbd/cache/watched_data.sab
2010-01-06 23:04:52,071::INFO::[_cplogging:55] [06/Jan/2010:23:04:52] ENGINE Started monitor thread '_TimeoutMonitor'.
2010-01-06 23:04:52,095::INFO::[postproc:133] Saving postproc queue
2010-01-06 23:04:52,112::INFO::[__init__:637] Saving data for postproc1.sab in /etc/SABnzbd/cache/postproc1.sab
2010-01-06 23:04:57,142::ERROR::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Error in 'start' listener <bound method ServerAdapter.start of <cherrypy.process.servers.ServerAdapter object at 0x20fbfa10>>
Traceback (most recent call last):
  File "/root/src/SABnzbd-0.5.0Beta4/cherrypy/process/wspbus.py", line 147, in publish
    output.append(listener(*args, **kwargs))
  File "/root/src/SABnzbd-0.5.0Beta4/cherrypy/process/servers.py", line 55, in start
    wait_for_free_port(*self.bind_addr)
  File "/root/src/SABnzbd-0.5.0Beta4/cherrypy/process/servers.py", line 260, in wait_for_free_port
    raise IOError("Port %r not free on %r" % (port, host))
IOError: Port 9090 not free on '192.168.0.11'

2010-01-06 23:04:57,373::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Serving on 192.168.0.11:8080
2010-01-06 23:04:57,384::ERROR::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Shutting down due to error in start listener:
Traceback (most recent call last):
  File "/root/src/SABnzbd-0.5.0Beta4/cherrypy/process/wspbus.py", line 184, in start
    self.publish('start')
  File "/root/src/SABnzbd-0.5.0Beta4/cherrypy/process/wspbus.py", line 147, in publish
    output.append(listener(*args, **kwargs))
  File "/root/src/SABnzbd-0.5.0Beta4/cherrypy/process/servers.py", line 55, in start
    wait_for_free_port(*self.bind_addr)
  File "/root/src/SABnzbd-0.5.0Beta4/cherrypy/process/servers.py", line 260, in wait_for_free_port
    raise IOError("Port %r not free on %r" % (port, host))
IOError: Port 9090 not free on '192.168.0.11'

2010-01-06 23:04:57,393::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Bus STOPPING
2010-01-06 23:04:57,440::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('192.168.0.11', 8080)) shut down
2010-01-06 23:04:57,448::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('192.168.0.11', 9090)) already shut down
2010-01-06 23:04:57,461::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Stopped thread '_TimeoutMonitor'.
2010-01-06 23:04:57,468::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Bus STOPPED
2010-01-06 23:04:57,475::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Bus EXITING
2010-01-06 23:04:57,482::INFO::[_cplogging:55] [06/Jan/2010:23:04:57] ENGINE Bus EXITED
2010-01-06 23:04:57,489::ERROR::[SABnzbd:234] Failed to start web-interface
2010-01-06 23:04:57,497::INFO::[__init__:279] SABnzbd shutting down...
2010-01-06 23:04:57,505::INFO::[__init__:637] Saving data for bookmarks.sab in /etc/SABnzbd/cache/bookmarks.sab
2010-01-06 23:04:57,513::INFO::[urlgrabber:98] URLGrabber shutting down
2010-01-06 23:04:57,528::INFO::[__init__:637] Saving data for watched_data.sab in /etc/SABnzbd/cache/watched_data.sab
2010-01-06 23:04:57,536::INFO::[dirscanner:281] Dirscanner shutting down
2010-01-06 23:04:57,868::INFO::[downloader:452] Shutting down


Now I've reinstalled beta 4, and also changed the default ports to 7070 and 8000 - and now it works (don't know why). So it's now running overnight.

My initial impression are that it's really quite slow compared to the native SABnzbd, despite using a premium server. Not sure where the hangup is, though expect it to be the NV, which is now starting o be a bottleneck in many things.

regards


Gareth

[chinchin]

Sorry snapper, I didn't see your reply until just now (I was expecting email notificaitons but they never came .. ho hum).

Anyway you aren't the first person who has mentioned that they are slow actually but I have noticed that when a full download has finished the overall stats don't appear to be that bad. Although I'm surprised the Beta5 didn't work, I did have the same problem as you but a full restart solved the issue.

Have you tried using the new BETA 6 yet? I think there might be DNS resolution issues but not quite the same ones that are being stated on the forum, I think the BETA6 uses IPv6 but the ReadyNAS NV+ doesn't appear to support it.

snapper now that you have it working with BETA 4 have you tried upgrading back to beta 5?

[mrchris76]

hi guys, anyone having issues with their readynas duo, the new 0.5.0 release of sabnzbd and the version of unrar?

The one I have via the apt-get method is "UNRAR 3.50 beta 3 freeware" This appears to be old and doesn't support some switches sabnzbd wants to use, and results in failed unpacking of downloads. I looked around the rarlab.com site and couldn't see any source code that might be suitable (well there was source but no makefiles etc so no use to me)

Guessing all other Duo users are having this, whats the solution? I don't want to have to go back to an old RC really.. but thats the only way I think at the moment

Cheers

[chinchin]

Hi,
# For newest RC6 then a new unrar needs to be installed - this can be carried out post apt-get install unrar
  1. apt-get install g++
  2. Go to /root/src/
  3. wget http://www.rarlab.com/rar/unrarsrc-3.9.9.tar.gz
  4. gunzip unrarsrc-3.9.9.tar.gz
  5. tar -xvf unrarsrc-3.9.9.tar
  6. cd unrar
  7. mv makefile.unix makefile
  8. make
  9. Now replace current unrar binary, which unrar will display location. Rename said unrar file to unrar.old.
  10. Copy recently made unrar binary to the location of the previously renamed binary.
Forgot to post the update before, apologies.
Hope this works for all you guys.

[mrchris76]

Thanks for this, will have to try when back at home. I just made the grave mistake up adding a new line to source.lst and doing an apt-get upgrade  ctrl-c when i realised what I had just done, think i've hosed some things. Ahh firmware reinstall time possibly.

Will post back once i've followed your updated instructions for unrar anyway.. thanks 

[mrchris76]

Awesome, unrar now upgraded to v3.92 freeware and sabnzb now unpacking downloads, Thanks again for your help!

I didn't hose my duo either, managed to fix it