SABnzbd Forums

I have an odd issue with SAB. My server shows no issues when I test it, and I am connected to the internet.

However, my downloads will never start. It always sits at "Idle," and nothing is paused.

EDIT: also I show no warnings in the logs. From what I can tell SAB sees no issues with anything.

Possibly a queue corruption.
If you still have the NZBs, it's best to erase the queue.
Stop SABnzbd, start it again with
WindowsKey-R and
"c:\program files\SABnzbd\SABnzbd.exe" --clean
(Assuming you have Windows)
Then add the NZBs again.

Thanks for this. But its weird. The download did start about 5 minutes after I posted that on its own. It seems like sometimes the downloads do not start right away, but will begin randomly.

Happened to me also, was enough to chenge the order of the nzbs. I still think this should be investigated as it looks as some sort of bug with the latest version only.

This can happen in earlier versions too.
That's why 0.6.0 will get a different queue organization.

my ubuntu version seems to be exhibiting the same behaviour....is there a command i can run to sort this?

Sab version 0.5.6

The blunt method is starting once with:
./SABnzbd.py --clean

You'll lose the queue.

managed to get it to start downloading again by forcing disconnect (in the web interface under connections) then restarting via the init.d script
dont know why it was hanging and saying it was downloading in the web interface but not actually doing anything...only seems to have been a problem since i upgraded to 0.5.6

benharvey1985 wrote: only seems to have been a problem since i upgraded to 0.5.6

Does it happen repeatedly?
Could be just a one time accident.
There were no changes to the download queue between 0.5.5 and 0.5.6

seems to be happening almost every night now, and i think i came from 0.5.4 RC(something) i was thinking about doing a complete uninstall and reinstall...incase of any file that could be causing this...

and again thank you shypike for your continued support

Same thing been happening to me and I also know of somebody else with the same problem

What helps to tackle this is more details.
Also checking which exact release introduced this in your situation will help.