SABnzbd Forums

Hey guys, Hope my subject line was of use, I didnt really know what else to put.

So here is the problem, no matter how I add an NZB, it will get downloaded and placed in the history with a status of Queued. This all started after I placed an NZB in the blackhole(Watched) folder and it was just a single mp3. Once that NZB was finished, it was placed in history w/ queued status just like everything after it.

----

Ok, I just thought to check if par or rar.exe were locked up or something and it turns out there were 2 SABs running. I am currently using a temp setup and have not created a service for this machine as it wont be setup this way for long. So I'll post this anyway in case someone else has the problem above. 

Ok, this is an official bug now...

I have only tested this with mp3 files, but...

Newzbin --> do a raw search and find a small mp3 --> save it into your blackhole directory --> it downloads and is placed in history as "Queued"

Every subsequent download is then downloaded and placed in history as "Queued"

Restart SAB --> same thing.

Delete all items in history --> shutdown sab --> Receive EXE error as follows...

Exception in thread Thread-1:
Traceback (most recent call last):
  File "threading.pyo", line 488, in __bootstrap_inner
  File "sabnzbd\postproc.pyo", line 133, in run
  File "ntpath.pyo", line 67, in join
  File "ntpath.pyo", line 53, in isabs
  File "ntpath.pyo", line 119, in splitdrive
TypeError: 'NoneType' object is unsubscriptable

Now start SAB again ... all downloads fine ... unless you download another mp3 via Blackhole.


Hope this helps someone. I am in the process of learning python but I doubt i'd be any help any time soon.

And a known bug, not limited to small MP3 files.

Work-around: use the user-defined categories instead.
In Config->Categories there's a link that will fill the categories in newzbin-style.
You only need to add the folders for each category.

The "Create Category Folders" (now in Config->Newzbin) option will be removed from
the next release. This functionality can be obtained using user-defined categories with
more flexibility.

shypike wrote: And a known bug, not limited to small MP3 files.

Work-around: use the user-defined categories instead.
In Config->Categories there's a link that will fill the categories in newzbin-style.
You only need to add the folders for each category.

The "Create Category Folders" (now in Config->Newzbin) option will be removed from
the next release. This functionality can be obtained using user-defined categories with
more flexibility.

Ah... man I'm stupid. lol. I thought I was all onto something. Thanks for the explanation... oh and Thanks a million for the software/support/continued efforts put into this project... all of you.

Of course you are not stupid.
It is a bug after all, so if anyone is stupid it's the one who put the bug in (me in this case).

I am having this problem too. But I don't want to delete the stuck items..

I have many gigabytes stuck in the History marked as queued. I do not want to delete them as I have paid for the bandwidth already and it would take a long time to re-downlaod them. Is there a way I can get it unstuck without wiping the history? So that these files get processed.

Thanks
James

Are the downloaded files still in "incomplete"?
Has anything been moved to "complete".
What happens to the items when you restart SAbnzbd?

I am also having a problem with items stuck as 'queued.' The items are not being moved to the 'incomplete' dir despite all downloads apparently complete. So now I have a 'cache' dir withbover 9,000 files. I hit the shutdown button, but Sabnzbd is unable to close. 0.4.0RC4, Linux, 32mb, 266mhz nas.

*Update: resorted to killall python to shut down sabnzbd. Upon restart, the queued items begin processing, cache is cleared but the result are empty folders with the correct item names on them. just noticed on in the log screen: '2008-06-20 10:53:57,910 ERROR [postproc] Error removing workdir.'

shypike wrote: Are the downloaded files still in "incomplete"?
Has anything been moved to "complete".
What happens to the items when you restart SAbnzbd?

I cannot tell what went wrong.
However, running on 32 MB might be asking for trouble.
SAbnzbd can easily take 32MB or more memory, it wasn't exactly designed with minimal memory use in mind.
Example: if SABnzbd processes an 8 MB NZB file it will use (at least for some time) 16 MB extra memory.

Have you taken all memory preservation precautions?
- Set "Article Cache Limit" to 0
- Select "Only get articles for top of the queue" option
- Select "Pause downloading during post-processing" option
- And for safety's sake, enable "Enable periodic save"

But even then I would be worried with only 32MB.

I know it is demanding a lot considering the spec of my NAS, but to be fair I've processed well over 100gb of items using SABnzbd in the past. I thought maybe it was a settings issue, but I know believe it is related to one of the newer Release Candidates as Beta 4 (the last version I used before upgrading) was worked fine. I'll backtrack and let you know.

Thanks for taking the time to help.

Lost101

*Update: RC4 is working again when I ran SABnzbd using Python 2.5 (instead of 2.4). I guess that is how I had been running SABnzbd prior to my holiday from it's goodness

I'm a bit surprised by this, because some people claim that on some NAS-devices they specifically need Python 2.4.
Well, at least it works for you now.

Actually the size of the download doesn't affect the memory use very much.
I was referring to the size of the NZB file itself.

Unfortunately this problem hasn't gone away. When using python2.5, the NAS will freeze when I have too many items queued in SABnzbd. I have gone back to using python2.4. Oddly, the 'Item stuck as Queued' problem also occurs when I try earlier releases of SABnzbd (the 0.4.0 RCs and betas and 0.3.4) which makes me suspect the problem is related to a change in one of the components that SABnzbd relies on. Could you make a suggestion? The  logs show no errors. I have had SABnzbd running successful in the past, which makes this even more frustrating.

I hope you can help.

Lost101

I only know that some NAS users have gone back to CherryPy 2.2.1, instead of 2.3.0.
For this: remove the "embedded" cherrypy in SABnzbd's program folder
and install CherryPy-2.2.1 as a Python module.
I don't know why this makes a difference, it's just what was reported back by some users.