SABnzbd Forums

The program runs on a Ubuntu 8.04 system.
My problem is, that after a download is finished and need to be repaired, the download goes back from the history to the queue. In the queue the download is still standing on 0 MB left and never finish. All other downloads wan't start again and I need to go to the Settings and need to Repair sabnzbd, after that the download goes ahead and is finishing correctly.
Is there any solution for this problem?

Greets altohr

Do you have multiple servers defined, some of which aren't very reliable?

I have only a hitnews.eu server with 5 connections and it's reliable.

altohr wrote: Is there any solution for this problem?

You probably should upgrade to release 0.6.0 Beta3.

Please read the header... I have the problem with the 0.6.0 Beta3
But i had the problem also with the Beta 2. With the old stable version I hadn't this problem.

Is this a general problem or does it occur with specific NZB files?
If so can you email one to bugs at sabnzbd.org ?

Good morning!

I experience the same problem (although I can't tell you exactly which Version I'm using at the moment ... not in front of the computer), I yesterday and today had the problem that when I download some larger files (in my case app. 4-5 GB) and one of the finished DL's had to be put back into the queue, the DL speed decreases to 0 and everything is stopped.

The only thing that helped for me in that case was deleting the queue, restarting sabnzbd and adding the nzb's again.

Greetings

Without more info there's not a lot I can do.

Tell me what you need and I can try to get it today afternoon/evening.

Any information about repeatability.
Specific NZBs?
When a job hangs in the queue, what does the details show?
Preferably use the Classic skin, where expanding shows all files
and clicking the title will show all files to be downloaded.
Your server setup (primary only or with backup servers, do some fail occasionally?)
How is "only download from the top of the queue" in Config->Switches set?

Hi,

the problem is not really repeatable. A nzb didn't work for me yesterday, today it went through. Maybe it only happens when you had a lot MB downloaded in other nzb's previously.

For the rest I will keep an eye open and post it.
If you'd like you can take a look on my screen when it happens again (mail me your Skype/ICQ data and I will add you so I can contact you), then we could start a TeamViewer session.

Greetings.

[EDIT]
I use only one server
"only download from the top of the queue" is checked

MadKombat wrote: "only download from the top of the queue" is checked

At least switch this one off so that one job doesn't block the whole queue.
(The option is really only for systems with tiny memories).

Turned it off, currently still hanging.
If you#d like to sneak a peak, tell me. I can wait some hours before I continue.

On the outside there's nothing much to see for me.
If you look at the details of the hanging NZB, are any files still listed?
If you look at the content of the "incomplete" folder, are all expected files already present?
Can you zip up the SABnzbd logfiles and email them to bugs at sabnzbd.org ?

Generally there are two likely causes.
There's an inherent problem in SABnzbd that it wants to hear from each
potential server explicitly that it doesn't have a missing article.
Long and complex reasoning, but I think we can rule this out here,
because you have only one server.
Should you have multiple servers, the trick is to declare any potentially
unreliable server as "optional".

There's a problem present in 0.5.6: a job that has no more
articles to download will lack the trigger to leave the queue.
One obvious example is an NZB file with no articles and files at all.
In 0.5.6 there will never be a trigger for it to leave the queue, because no article
ever comes in, because none was ever asked for.
For 0.6.0 this problem is solved, well at least we attempted to solve it.
It's always hard to prove the absence of a problem.
So what I'm looking for is whether a job is sent back to the queue without
the need to get further articles, which somehow lets the old problem come back.

Mail is sent