Page 1 of 1

Completed? But spinning wheels

Posted: January 30th, 2015, 3:19 pm
by AtariBaby
Hi
Image
Version: latest
OS: ubuntu 14.04 fully updated
Install-type: repository?
Skin (if applicable): Default
Firewall Software: No software firewall
Are you using IPV6? no
Is the issue reproducible? yes

Sorry I suspect you get asked this a lot, but I couldn't find the solution on my own.

I have two tiny comic book files that are seemingly hanging up Sab. Everything will be a spinning wheel until I stop the service and restart. But when I do, the bad processes eventually gum it up again. The script log on that file shows "Successful!" which is the way the processing script always reports a successful completion. This script has otherwise worked flawlessly for ages.

What should I do about this, and if it's a matter of removing some file, where are they located? (I'm largely ignorant of the magic that makes Sab work, it works that well)

Re: Completed? But spinning wheels

Posted: January 30th, 2015, 3:43 pm
by AtariBaby
Update: I deleted the folders of the two trouble comics from the "incomplete" folder. Wasn't sure if that was sufficient or even the right thing to do.

Re: Completed? But spinning wheels

Posted: February 2nd, 2015, 3:23 am
by shypike
It seems that your script hangs for some reason.
Since I don't know what happens inside the script, what can I say?
A hanging script can best be stopped with the task manager of the OS.

Re: Completed? But spinning wheels

Posted: February 2nd, 2015, 12:18 pm
by AtariBaby
If you're talking about killing the sabnzbd process, I did that but the problem kept recurring. For whatever reasons, deleting the relevant folders in /incomplete stopped the issue. I can live without those two. I'll just chalk it up to an issue with those files and the script and not good old sturdy sab.

Thanks for replying. I appreciate all the help you provide here!

Re: Completed? But spinning wheels

Posted: February 2nd, 2015, 3:18 pm
by shypike
Assuming it's actually the script that hangs, then the best solution is to stop the script.
SABnzbd will then declare the download as failed, but it will
still be unpacked and stored in the __failed__NAME folder.