SABnzbd+ won't download anymore.

[coolrunnings]

Since last night SABnzbd won't download any items anymore.
Until last night I had no problems whatsoever with downloading.
This is the error message I see in the errorlog:

2009-03-29 15:21:37,138
ERROR
[downloader] Exception?

2009-03-29 15:21:37,138
WARNING
[downloader] Thread 3@newsserver:119: server broke off connection

I've searched on the Internet and this forum, but I cannot find anything that can lead me to a solution.
Does anyone here have a solution

[shypike]

Try to stop and start SABnzbd.

If that doesn't help, restart SABnzbd from a command prompt, like this:

Code: Select all

"c:\program files\SABnzbd\SABnzbd.exe" --clean

This will wipe the (possibly corrupt) queue and history.

[DeXeS]

Don't know if im right but looks like the server broke the connection.. not sabnzbd. Did your subscription to your usenet provider ended/ is the usenet provider down?

[coolrunnings]

I've just downloaded Grabit to test that, and with Grabit I can download just fine.

[coolrunnings]

STarting SABnzbd with the parameter --clean did the job.

[shypike]

Don't know if im right but looks like the server broke the connection.. not sabnzbd. Did your subscription to your usenet provider ended/ is the usenet provider down?

No, it was some problem in SABnzbd. It looks like the downloader task crashed.

Code: Select all

2009-03-29 15:21:37,138
ERROR
[downloader] Exception?

[DeXeS]

ah oke my bad 

[coolrunnings]

Once again, I ran into above mentioned situation, so I starten SABnzbd+ with the --clear option again.
Putting al the NZB's back in the queue (sorted by name), categorize them, and after categorizing them, I sorted the queue by age and voila, no more downloading. Resorting the queue by name, and the downloading resumed.

So, my queue is now sorted by name so the download will continue, but there seems to be a little bug in the sorting mechanism which dauses downloading to stop.

[shypike]

So, my queue is now sorted by name so the download will continue, but there seems to be a little bug in the sorting mechanism which dauses downloading to stop.

Interesting, I'll see if I can reproduce this problem.
Just checking:
Is none of the jobs suspect, in the sense that you expect it to have mostly non-existing articles?
Are there any idle "newzbin fetching" lines?
Which release are you using? We will only fix problems in 0.4.8

Obviously, SABnzbd should still download despite this.
But more info will make the diagnose easier.

[shypike]

So, my queue is now sorted by name so the download will continue, but there seems to be a little bug in the sorting mechanism which dauses downloading to stop.

Interesting, I'll see if I can reproduce this problem.
Just checking:
Is none of the jobs suspect, in the sense that you expect it to have mostly non-existing articles?
Are there any idle "newzbin fetching" lines?
Which release are you using? We will only fix problems in 0.4.8

Obviously, SABnzbd should still download despite this.
But more info will make the diagnose easier.

It may also help if you send me a ZIP file with all NZB files in the queue.
[email protected]

[coolrunnings]

Hi,

I'm using the latest version 0.4.8.
I've just tried the following:

Sorting by Age and then drag a few other NZB's to the top of the queue to rule out a suspicious NZB-file.
All the files I dragged up to the top didn't trigger SABnzbd to resume downloading.
After sorting it back again by Name the downloading resumed at full speed.

I'll send a zip-file in the evening when I'm at home.

[Mr. Wilby]

I think I have the same problem. I had my queue also sorted by age, and just like the other report(s) I couldn't download anything....

After finding this page, I turned off sort-by-age and now it's downloading again. I'm using the most recently released version.

[shypike]

I did a few quick checks, but I cannot find anything wrong.

However, if you use age sorting the oldest job will be at the top.
If this job is beyond the retention time of your Usenet provider, it will hold up the queue
for quite some time.

How did you set the option "Only get articles for top of the queue" on Config->Switches?
If it is "on", then any problematic job at the top of the queue, will block the queue.
You should only set this option "on" when you have a system with very limited memory (like a NAS).

[Mr. Wilby]

Hi. Yes, I had that option enabled (I think it must be by default because I don't recall turning it on). However, I cannot reproduce this again right now so perhaps that is it...