SABnzbd Forums

Easy check #1: edit SABnzbd.py and change that line to cherryhost = '1.2.3.4'. Run SAB and see what port it binds too.

Wont start sab at all.

Saiya_Jin_Vegeta wrote:Easy check #1: edit SABnzbd.py and change that line to cherryhost = '1.2.3.4'. Run SAB and see what port it binds too.

Wont start sab at all.

As you run Linux and you know how to 'grep' and edit a file, I think you're not the average user. I therefor would expect something more elaborate than "Wont start sab at all.". I would expect something "Wont start sab at all; output on stdout is ... blabla ... .". And I would expect that you also run the other two checks. That way I think an analysis and pin-pointing the problem is easier.

However, I might be wrong about this.

There is a problem in the code for systems that have no proper resolve of the system's "node name".
SABnzbd falls back to 0.0.0.0, instead of localhost/127.0.0.1/::1
I'll correct that in the next release.

The only work-around now is to modify your /etc/hosts table so that it
resolves the name that is shown by the "uname -n" command.
This is a sensible thing to do in any case, because the "node name" should resolve.
Unfortunately this is an issue in many default Linux installations.

shypike wrote:There is a problem in the code for systems that have no proper resolve of the system's "node name".
SABnzbd falls back to 0.0.0.0, instead of localhost/127.0.0.1/::1
I'll correct that in the next release.

Is the first piece of code that I quoted in an earlier post?

Yes.

shypike wrote:Yes.

OK.

And can you have a look at the second piece of quoted code? "If 0.0.0.0 then set to 0.0.0.0" ... what's that?

The problem was in the first piece of code.
The second piece is correct, the line with the extra assignment to 0.0.0.0 is not needed, but the second line is.

shypike wrote:The problem was in the first piece of code.
The second piece is correct, the line with the extra assignment to 0.0.0.0 is not needed, but the second line is.

Yes, I know. So: remove that redundant line with the 0.0.0.0 assignment ... ?

Even tough I am not bin in the possibility to do the testing as "sander" asks, I am happy that the problem hopefully can be resolved.
Will test it when I am home again (this evening I hope)

Done it using this small tutorial (from opensuse fora):

In openSUSE,
You have to configure your Hostname properly in TWO places in YAST

- The Hosts file
YAST > Network Services > Hostnames
- The Network Configuration
YAST > Network Devices > Network Settings > Hostname/DNS tab
(Be certain that the "Change Hostname via DHCP" is <unchecked> or as it says DHCP will change how you're seen on the Network no matter what your local settings are.

Now it is working correctly.
Thanks for the tip -> My network is now also configured correctly