Page 1 of 1
14979d nzb blocks queue
Posted: January 5th, 2011, 2:32 pm
by jsd
Every once in a while, an nzb file I download (from binsearch.info) shows up as "14979d" in the Age column. When one of those files gets added to the queue, sabnzbd hangs when it gets to that entry. If I delete it, sab continues fine. What's going on there?
Re: 14979d nzb blocks queue
Posted: January 5th, 2011, 3:21 pm
by shypike
I sometimes get such files from newzbin.
When I check them, they turn out to be empty (as in "containing no files").
Due to a design problem in the queue, empty jobs will never leave the queue.
You can "fix" this by setting the option "Only Get Articles for Top of Queue" in Config->Switches to off.
This will prevent blocking of the queue.
You still need to delete the NZB from the queue.
Release 0.6.0 will fix this issue (but alas not the emptiness of the NZB).
Re: 14979d nzb blocks queue
Posted: January 6th, 2011, 1:26 pm
by jsd
shypike wrote:
I sometimes get such files from newzbin.
When I check them, they turn out to be empty (as in "containing no files").
Due to a design problem in the queue, empty jobs will never leave the queue.
You can "fix" this by setting the option "Only Get Articles for Top of Queue" in Config->Switches to off.
This will prevent blocking of the queue.
You still need to delete the NZB from the queue.
Release 0.6.0 will fix this issue (but alas not the emptiness of the NZB).
Thanks. This was indeed the problem - the nzb's were empty. Sounds easy enough to prevent adding empty/invalid nzb's to the queue in the first place. I'm a pretty good programmer. If I felt like diving into Python, where in the code would I look for the add-to-queue logic?
Re: 14979d nzb blocks queue
Posted: January 6th, 2011, 1:52 pm
by shypike
We're not planning any new 0.5.x releases.
That's the main reason.
We're preparing for the first Beta of 0.6.0, which doesn't have this issue any more.