SABnzbd Forums

Good afternoon,

A mate of mine wanted me to install sabnzbd on his linux server yesterday, hes not to good with linux but i am, hence why i installed it. Hes running Opensuse 11.1.

We had some problems right from the start, after an hour of searching it seemed that opensuse 11.1 uses python 2.6 and not 2.4/2.5. Ive recompiled python 2.5 into /opt/ and installed yenc/cherrypy/cheetah with the python 2.5 binary.
Most problems went away, the shutdown button again deems to work, it saved it settings and was working good for about 6 hours.

Right now, a few hours later (and sab still running with python 2.5), the problems return. Shutdown doesnt work anymore, save settings doesnt work anymore, all threads are disconnected from usenet even tho there is something in the queue.
The weblog and the sabnzbd log doesnt tell me much, the last message was an "unrar completed", followed by a lot of fetching bookmark messages (from newzbin). It does not try to connect to the usenet, even tho there is something queued.
This can be fixed by terminating sab (kill -9 pid) and then to restart sab, this workaround works briefly for about 15 minutes.

Python-2.5.4 compiled with Zlib support.
Cheetah-2.0.1 compiled.
CherryPy-2.3.0 compiled.
python-yenc-0.3 compiled.

unrar and par2 from repository.

Anyone knows what i could try to get it running as it should run?

Thanks in advance

I'm running into the same issue, it will not shutdown and saving settings never completes.  On the shutdown, I get the confirmation pop-up, the page says Initiating shutdown..., Firefox shows Loading.. on the tab, and Transferring data from 192....

I'm running Suse 11.1, python 2.6.0-2.16.  I can't say for sure which update caused it.

Unfortunately we have no experience at all with Suse 11.1 (except that more people complain about it).
Python 2.6 is not supported by us (mainly due to the many third party modules we use, few of which
have been verified for Python 2.6).

Given that SABnzbd runs OK on just about any other platform, I strongly suspect the problem is in Suse itself.

Some tips:
Do not use kill -9, it can easily corrupt the internal bookkeeping of SABnzbd., First try just kill or kill -3.
When you change the configuration, first pause downloading. Especially when you have
a large memory cache it will take a while before things get stable.
Make sure you have a proper unrar (3.71 or 3.80Final, absolutely not 3.80Beta2).

OK thanks.  I usually just let it go and it works fine.  The tips on the kill are good.  I porked the thing earlier .  Thanks again for a nice nttp client.