Items "stuck" in History?

[Clay]

I've got a problem where some items are stuck in a processing mode - I see one of the items is waiting for a script to finish even though the script is no longer running, and the other item is waiting for it.

I've tried restarting, is there another way to clear out those entries?

[shypike]

Alas no, the post-processing isn't supposed to hangup 
Does restarting SABnzbd resolve the issue? In the sense that post-processing no longer displayed as being active.

[Clay]

I've restarted several times, no luck

[shypike]

The easiest thing to do is start once with the --clean option (command line).
This will erase the queue and the history.
The 0.5.0 release will improve on this, but we're not going to fix 0.4.x in this area.

[Clay]

That did it. Thanks!

[superJ]

The easiest thing to do is start once with the --clean option (command line).
This will erase the queue and the history.

How do I start it with the "--clean" option? Sorry, this might be an absolut noob-question, but I really don't know, how to start with a "command line". But I might have simmilar problems like clay so I want to try this sollution. So could you provide me with a step by step instruction how to do this?
BTW I am using SABnzbd+ on OSX Leopard.

Thx in advance.

[shypike]

In OSX it's a bit tricky.
The alternative is to go to the hidden .sabnzbd folder (yes, it starts with a dot) and erase alll files in the cache subfolder.
You should first tell the Finder to show hidden/system files.

We really should add something in the Web-UI to do it.
On the other hand it's quite destructive...

[thefarmer]

I'm not sure if this is the same problem i'm having or not.
It seems that i have a couple of things showing as 'busy' in my history queue.  One is showing as "Not enough repair blocks, downloading all available (15 short) " and the other is showing as "trying to fetch 2 more blocks... "
Neither are doing anything whatsoever except having the swirly icon going round and round to the left.

Can i delete/stop/do anything with these entries?
Fortunately i changed the setting in sabnzbd so it doesn't pause and wait for these to finish processing.

thnx guys.

[shypike]

Could be crashed par2 sessions.
Does restarting SABnzbd help?
The alternative is to start SABnzbd with the --clean command line parameter,
this will erase the complete queue and history.'

[NoGood]

Thanks worked like a charm. First time user of Sabnzbd. Amazing that i can mess it up so quickly 
Slightly of topic, i restarted the item that i lost in the download queue. Its meant to download the files again right, and not resume?

[shypike]

SABnzbd is sensitive to incorrect termination, like stopping it with Task Manager or shutting down the system.
Crashes of the third-party post-processing utilities, like par2 and unrar are difficult to handle properly.

If you used --clean, SABnzbd should forget all of its past.