SABnzbd Forums

Im getting the following in my log each time i add an nzb file.

Exception in thread HTTPServer Thread-31:
Traceback (most recent call last):
  File "threading.pyo", line 488, in __bootstrap_inner
  File "threading.pyo", line 448, in run
  File "cherrypy\process\servers.pyo", line 75, in _start_http_thread
  File "cherrypy\wsgiserver\__init__.pyo", line 1644, in start
error: (10049, "Can't assign requested address")

Exception in thread Thread-8 (most likely raised during interpreter shutdown):

Im running 2 existances of Sab.exe, one on my server to do all the downloading, and then one on my desktop pc which really only exists to pass through the data. Im sure theres an easier way but i havent found it unfortunately. I dont believe i was getting the error until i updated to 0.6.2 the other day, and its there with 0.6.4 today too.
The config file doesnt appear to be incorrectly modified in any way from 0.6.0 but Im getting a pop-up error telling me to check the log, im certain it wasnt doing this previously, but maybe it was always erroring except now its more 'in-my-face' rather than in a log file i never check. I tend to spot the icon on my toolbar, and cos i stack toolbar icons there'll end up being 8-10 of the things hidding there 

The actual process all works, it adds to the queue just fine, but it insists on giving an error in the process.
If someone could help remove the error, or better yet tell me a better way to download an nzb and auto-queue it from another PC, i'd be very grateful.

Do you use one SABnzbd to upload NZB files to another system?
Isn't it more practical to use a Firefox add-on like nzbdStatus?

Which of the two gives the errors?
I assume the two instances are not sharing any data (like over a share),
because that's not supported.

Asside from automated queues with Sickbeard, if i manually add something to the queue then its done on a secondary PC. That PC has Sab installed and configured for the IP address of my server machine.
Its these manual additions which generate errors, both completely seperate installations, with the config file telling it the server location is the IP address of the other machine.


I have nzbdStatus on Firefox, its configured and tells me the live status of Sab, however i cant get it to add anything.
When i click on an nzb link, firefox pops up saying what do i do with it. I either download it, or open it with something (Sab in my case).
If i cancel, it does nothing.
If i open with Sab (local) then it adds it to my server queue perfectly, however recently ive been getting this error.

nzdbStatus Settings:
ticked 'Send NZB downloads to SABnzdb'
unticked 'Prompt before sending'
API key and IP test comes back successful.

Im having to resort to 2 installations of Sab because its been the only way it'll work so far.
My current 'bodge-job' does work, but i doubt its ideal, and ive noticed its giving a local error shortly after adding to the servers queue.

If you're using Windows there's a better hack.
Add this to your registry (after editing) on the PC that needs to send the NZB.
Ony after doing this, start any SABnzbd setting.

ok, made that edit in the registry, wasnt 100% sure what sort of value i was adding in there, but having added the edit it and then adding a file to the queue its gone on there and im yet to see an error popup, or any sign of the log file being created.
Seems to have done the trick , Thanks

Is there a way of using nzbdStatus so it does what it seems to imply it can do? It knows the Sab location, its allowed to download and add straight to queue, but really the only way i can make it work is by using a local installation of Sab and having that do the diversion. Im guessing nzbdStatus can do it, otherwise it wouldnt have half the settings on the first tab, it just doesnt seem to work though.


I also noticed i dont have SABnzbd running as a process on this (secondary) machine, never realised that. I expected it to be sitting there, almost pointlessly.

PaulC2K wrote: I also noticed i dont have SABnzbd running as a process on this (secondary) machine, never realised that. I expected it to be sitting there, almost pointlessly.

When SABnzbd can dump the NZB to another instance, it just exits after that.