(Unofficial) Ubuntu repository for SABnzbd+

[sander]

Indeed, automating that would make the instructions a bit more newbie-proof (albeit at the cost of becoming more susceptable for futile attempts to use the repo with unsupported/ancient versions of ubuntu). Done.

Code: Select all

echo "deb http://ppa.launchpad.net/jcfp/ubuntu $(lsb_release -c -s) main" | sudo tee -a /etc/apt/sources.list

Aha, there's a "lsb_release" command. I didn't know that. Your solution is much more beautiful than mine with grep and awk. Great.

Code: Select all

sander@ubuntu810:~$ lsb_release -c -s
intrepid
sander@ubuntu810:~$ lsb_release --help
Usage: lsb_release [options]

Options:
  -h, --help         show this help message and exit
  -v, --version      show LSB modules this system supports
  -i, --id           show distributor ID
  -d, --description  show description of this distribution
  -r, --release      show release number of this distribution
  -c, --codename     show code name of this distribution
  -a, --all          show all of the above information
  -s, --short        show requested information in short format
sander@ubuntu810:~$ 

[rascalli]

I installed it on my new server , and this is so easy ....

Tx for this !!   

[jcfp]

0.4.5~rc1 0.4.5~rc2 0.4.5 final has been uploaded. No major changes on the packaging side.

[daniel_owen_uk]

Just wanted to say a quick thanks for this, it's attempts like this that make linux a much more viable alternative to windows every day.

Very easy to install, great work.

[sander]

Strange:

http://[::1]:8080/sabnzbd/ does work for SABnzbd when I run  ./SABnzbd.py from the extracted tar.zip, but it won't work when I run sabnzbdplus (both from CLI and as a daemon) from the unofficial Ubuntu package.
http://localhost:8080/sabnzbd/ works on both variants.

On Ubuntu 8.04, same version of SAB* (0.4.5RC2), using the same ini file, no firewall, full IPv6 connectivity, etc

Tips?

PS: The same is true for the full IPv6 address: http://[2001:5c0:8fff:fbaa::45]:8080/sabnzbd/ does work for the plain source sabnbzd, not for sabnzbdplus, but let's start easy with the ::1 address as that's easier.

Code: Select all

sander@ubuntu804:~$ wget http://[::1]:8080/sabnzbd/
--19:05:45--  http://[::1]:8080/sabnzbd/
           => `index.html.3'
Connecting to ::1:8080... failed: Connection refused.
sander@ubuntu804:~$ 

sander@ubuntu804:~$ ping6 ::1
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.057 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.091 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.089 ms

--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.057/0.079/0.091/0.015 ms
sander@ubuntu804:~$
sander@ubuntu804:~$
sander@ubuntu804:~$ telnet ::1 8080
Trying ::1...
telnet: Unable to connect to remote host: Connection refused
sander@ubuntu804:~$ 

[jcfp]

I think what you describe happens because of minor differences between the versions of cherrypy used in those two cases. Running 'sabnzbdplus' will use whatever is packaged in ubuntu (2.2.1-4 on hardy), while running from the extracted sources will instead use the cherrypy files included in the release (probably version 2.3). If you want to test, run from the sources after deleting the included cherrypy directory and see how it behaves then.

[sander]

It does ring a bell, however:

In older SABs with the older cherrypy, http://[::1]:8080/sabnzbd/ *did* work. Only the newsserver could only be IPv4-only. With current SABs, the newsserver can be IPv6 too.

And, on my Ubuntu 8.10, 1) I see the same behaviour (http://[::1]:8080/sabnzbd/ unreachable with sabnzbdplus from the ubuntu package) and 2) the cherrypy seems to be 2.3 and there's no cherrypy 2.2 (AFAIK). See below.

On top of that, it looks like the cherrypy directory from the official sabnzbd tar gz package, does not contain cherrypy executables?

Code: Select all

sander@ubuntu810:~/SABnzbd-0.4.4$ locate cherrypy | grep -i 2.3
/usr/share/python-support/python-cherrypy/CherryPy-2.3.0-py2.5.egg-info
/usr/share/python-support/python-cherrypy/CherryPy-2.3.0-py2.5.egg-info/PKG-INFO
/usr/share/python-support/python-cherrypy/CherryPy-2.3.0-py2.5.egg-info/SOURCES.txt
/usr/share/python-support/python-cherrypy/CherryPy-2.3.0-py2.5.egg-info/dependency_links.txt
/usr/share/python-support/python-cherrypy/CherryPy-2.3.0-py2.5.egg-info/top_level.txt
sander@ubuntu810:~/SABnzbd-0.4.4$ locate cherrypy | grep -i 2.2
sander@ubuntu810:~/SABnzbd-0.4.4$ 
sander@ubuntu810:~/SABnzbd-0.4.4$ 

[shypike]

On top of that, it looks like the cherrypy directory from the official sabnzbd tar gz package, does not contain cherrypy executables?

There's no such thing as CherryPy executables, CherryPy is a pure-Python module. Only the PY files are needed.
On Vista at least http://[::1]:8080/sabnzbd/ works fine.

[jcfp]

Exactly where and how you can connect to the interface depends on where the builtin web server is listening: the host and port can be defined in the ini, through the --server option, or use the default value of localhost:8080 (use "netstat -lnt" to verify). Unfortunately, what "localhost" translates into, whether ipv4 or ipv6 is preferred, etc., depends on the OS, browser, the content of the hosts file, and (possibly!) the cherrypy release or even sabnzbd's code. In the example you mentioned earlier, the only difference would appear to be the cherrypy version used, making it the more or less expected culprit.

The packaged version is not patched in any way that would affect what host it listens on, or kill it's capability of listening on ipv6; in fact, specifying an option like "--server [::]:8080" makes it listen on all ipv4 and all ipv6 on my system.

[sander]

Interesting: sabnzbdplus (thus: the SAB from the unofficial Ubuntu package) *does* connect outward to news.ipv6.eweka.nl. So sabnzbdplus does do IPv6, is not IPv4-only.
So "ipv6 unaware" is not the explanation it's refusing connections on http://[::1]:8080/sabnzbd/

Code: Select all

2008-11-07 23:10:56,914::INFO::[downloader] Thread [email protected]:119: [email protected] done
2008-11-07 23:10:56,915::INFO::[downloader] Thread [email protected]:119: fetching [email protected]

sander@ubuntu810:~/.sabnzbd/logs$ 
sander@ubuntu810:~/.sabnzbd/logs$ 
sander@ubuntu810:~/.sabnzbd/logs$ ps -ef | grep -i sabnzb
sander    5113     1  0 19:35 ?        00:00:14 /usr/bin/python -OO /usr/bin/sabnzbdplus --daemon
sander   21852  6644  0 23:11 pts/0    00:00:00 grep -i sabnzb
sander@ubuntu810:~/.sabnzbd/logs$ 

[jcfp]

Where cherrypy is serving the program's web interface is completely unrelated to the news servers being on ipv4 or ipv6.

[sander]

Strange, after filling out "0.0.0.0" in Config -> General -> Web Server Host, sabnzbdplus is listening on ::1 too ... Strange. (Even hard to believe: sabnzbd and sabnzbdplus use the same ini, and one was IPv6 listening, the other not.)

Anyway:

Looking back at my CLI logging, the non-IPv6 serving sabnzbplus shows this:

07/Nov/2008:18:50:17 HTTP INFO Serving HTTP on http://localhost:8080/
2008-11-07 18:50:17,385::INFO::Lauching browser with http://localhost:8080/sabnzbd
127.0.0.1 - - [07/Nov/2008:18:50:17] "GET /sabnzbd HTTP/1.1" 302 - "" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3"

The IPv6 serving sabnzbd and sabnzdplus show this:

07/Nov/2008:18:54:15 HTTP INFO Serving HTTP on http://0.0.0.0:8080/
2008-11-07 18:54:15,781::INFO::Lauching browser with http://localhost:8080/sabnzbd
::ffff:127.0.0.1 - - [07/Nov/2008:18:54:15] "GET /sabnzbd HTTP/1.1" 302 - "" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3"

Just by looking at the CLI logging, you can tell whether SAB is serving IPv6 requests on it's web interface. The strange, unexplained part is that with the same ini, the two SABs were showing different loggings.

So: Problem disappeared.

[jcfp]

0.4.6~rc2 0.4.6 final is on the way, package changes compared to 0.4.5:

• Made init.d script also accept nonexistent ini file (allowing the program to create it in the given location).
• Added support for jaunty (ubuntu 9.04). Very early ubuntu alpha release testers: enjoy and let me know all bugs.

Apart from that, the admins of the launchpad ppa service that hosts this repository seem to be getting closer to fixing the bug that causes the "unauthenticated packages" warning. Hopefully more on that soon.

[jrebeiro]

After installing and editing /etc/default/sabnzbdplus to use a specific user account I get the following when trying to start sabnzbd:

* Starting SABnzbd+ binary newsgrabber
Error:
  I refuse to fork without a log directory!
                                                                         [ OK ]

I am sure this is a permissions thing but I don't know what files/dirs to grant this user account permissions to.

I did verify that ~/.sabnzbd/* is all owned by the user I specify in /etc/default/sabnzbdplus

Also, the init.d script should report [FAILED] rather than [OK] in this scenario.

[jrebeiro]

*SOLVED*

sabnzbd tries to create folders/etc. in paths relative to the sabnzbd.ini file. I placed my file in /etc/sabnzbd.ini and the script was trying to create /etc/cache /etc/logs etc. When specifying absolute paths in sabnzbd.ini everything worked fine but web GUI still showed In "/etc" under Folder configuration.

Perhaps sabnzbd.ini should allow you to specify a base_path for everything.

I ended up moving my .ini to the root of where I wanted all the subfolders to go and everything is happy