SABnzbd Forums

I was about to put in a feature request to disable, but not remove, a server, when I noticed this entry in the RC2 changelog:

Fixed
Servers that were set to 0 connections (to stop them) caused sometimes problems

I was wondering if this fix might resolve the issue I was having. That is when a (usually fill) server is not working and a nzb is waiting for it to complete the download and move on to processing it. Currently setting the server to 0 Connections doesn't resolve the problem and the server must be removed before SABnzbd will continue.

Are you now actually using RC2?

What you describe should be solved by RC2.

Sorry, I should have made it clear I was using 0.3.3. I was just checking the changelogs to see if this problem was addressed before I brought it up.

Thanks for the answer and you work on SAB.

Wait a few days for 0.4.0RC3 to arrive.

I'm looking forward at RC3; With 0.4.0 RC2, my downloads still stall at about 1 MB when one server is not usable. It looks like SAB only wants to rely on the non-usable server. Proof; the connection overview shows this:

#  news.ipv6.eweka.nl:119: 0

    * Thread #1 -> 48066492$1$20033$[email protected] -> 1bbb.nzb
    * Thread #2 -> 4806648c$2$20033$[email protected] -> 0ccc.nzb
    * Thread #3 -> 48066493$3$20044$[email protected] -> 1ddd.nzb

# sslreader.eweka.nl:563: 0

In other words: the funcitonal newsserver sslreader.eweka.nl is ignored. :-(

PS: after setting the number of connections of the non-functional server to 0, the download completes.