SABnzbd Forums

Hi

Am trying to install sabnzbd on a friends DS212J using packages created for the Diskstation, and it installs fine. The service starts, and when clicking through to the sabnzbd page (port 9200), the wizard starts as normal, all settings are input and tested, and then sabnzbd restarts, and from there on in, cannot connect ever again! All I get is a 'server cannot be found' message.
So I uninstalled, and tried a different version also created for the Diskstation, install, and the exact same thing happens. This is all trying to connect to sabnzbd via the LAN (192.168.x.x:9200/sabnzbd etc).
Am I doing something glaringly wrong? Is there something else I should be doing? I even opened up two ports on my router for sabnzbd, made no difference.

Any help/pointers gratefully appreciated - might help me sleep better too!

Is sabnzbd running at all? To check, log in on the synology with ssh or telnet, and type "ps -ef | grep -i sabnzb"

And "netstat -apon | grep -i listen | grep -vi listening" will give you an overview: on the right hand side, is there a program "python" or "sabnzbd"? If so, what's on the left side: which IP address and port?

Thanks for reply sander, will check on this when I get home...am pretty sure the service is running, according to the synology package centre it is, but will run the ps & netstat commands once I get back home tonight, and will post back the results, as I'm not very Linux savvy!

hi sander

Tried these commands when got home. The ps-ef one dispayed the following
DiskStation> ps -ef | grep -i sabnzbd
ps: invalid option -- e
BusyBox v1.16.1 (2012-03-07 15:47:21 CST) multi-call binary.

Usage: ps

Report process status

Options:
w Wide output

DiskStation>
Tried ps and one of the lines is
14481 sabnzbd 268m S /usr/local/python26/bin/python /usr/local/sabnzbd/sh
so looks like a process is running?

The netstat command displayed the following:

DiskStation> netstat -apon | grep -i listen | grep -vi listening
netstat: invalid option -- o
BusyBox v1.16.1 (2012-03-07 15:47:21 CST) multi-call binary.

Usage: netstat [-laentuwxrWp]

Display networking information

Options:
-l Display listening server sockets
-a Display all sockets (default: connected)
-e Display other/more information
-n Don't resolve names
-t Tcp sockets
-u Udp sockets
-w Raw sockets
-x Unix sockets
-r Display routing table
-W Display with no column truncation
-p Display PID/Program name for sockets





Seems like it doesn't like that command, so I did a netstat -a and one of the lines is :
tcp 0 0 localhost:9090 0.0.0.0:* LISTEN which is the sabnzbd port, so I presume something is right somewhere but not 100%.

Any ideas?

Cheers

"tcp 0 0 localhost:9090 0.0.0.0:* LISTEN": good, SABnzbd is running, and it's listening on port 9090. However ... it's only listening locally on the Synology machine, so you cannot access it from other machines on the LAN. That is not what you want.

Solution: stop SABnzbd, then find the file sabnzbd.ini somewhere on the synology, open it with an editor and find the first occurence of "host". That will say "host = localhost". Change that line to "host = 0.0.0.0", save and exit the file. Then start SABnzbd. You can now access it from other systems on the LAN.

(Explanation what has happened: at the first start of SABnzbd you got the SABnzbd wizard, right? If so, you filled out the default setting "only listen on this host" or something like that. You should have chosen "access to other systems" or something like that)

So I hope you can find the file sabnzbd.ini on the Synology machine. Some googling ... maybe it is /opt/share/SABnzbd/SABnzbd.ini

HTH

That actually makes sense now you've explained it, about access from this pc only, or any pc! It just didn't click that this is what is needed. Will try this tonight when back home.

Thanks for your help so far

Sander

Many thanks for your help with this, the fix you suggested worked like a charm. All working sweet now, and can sleep again!

Thanks again

Mike