sabnzbd stuck on Running script: sabToSickBeard.py

[erann]

Hi there ,
There is one episode that I just noticed is stuck in queue on this script.
I already deleted the files manually from the sabnzbd download folders , and restarted the program , but file still shown on queue as "running script" and nothing happens.
This is going for 2 days already and because of that the rest of the files in history queue are not being processed and move to the correct location
please advice how to fix or how to reset entire HISTORY queue

thx.

[shypike]

1.
Remove the script folder in Config->Folders
Restart SABnzbd

or

2.
Stop SABnzbd.
Go to the "temporary download folder" and delete or rename the folder associated with the stuck job.
Restart SABnzbd.

[erann]

thx ,
i fixed it by running with -c command.

[shypike]

thx ,
i fixed it by running with -c command.

Yeah, that will help too, but it's a bit of a blunt instrument.

[abeam89]

Does anybody have a more optimal solution to this issue? I ran into it, and nothing that I have found anywhere indicates there is a better way to resolve this. I tried shypike's two suggestions without success. I would really prefer not to have to clear everything because of this.

I will note that my autoProcess config is not the issue. I have been using this configuration for many months without ever encountering this trouble.

Because of the sudden occurrence, I'm also wondering what exactly might have caused this to happen.

Any help is greatly appreciated. Please let me know if you guys would like to take a look at logs or anything, but I'm not sure I have enough to be useful based on what I parsed through.

[abeam89]

Well I've managed to resolve the problem. I'm still not sure of the source. I repeatedly tried restarting both SABnzbd and Sickbeard without success, but that never seemed to get me anywhere.

However, something that happened during a Windows troubleshooting step #1 (reboot) got me up and running again. It's a shame I had to reboot since I had a new uptime record going, but I was to the point it was worth trying to keep from losing my history.

If anyone does know of an alternative method for resolving this I'm sure it would help a lot of people out if they would post it here. I will note that it seems a common problem is mis-configuration of the autoProcessTV.cfg file.

For now, I'm adding reboot to my troubleshooting list as a last-ditch effort before clearing the history.

The resulting list as far as I know for troubleshooting this issue is now the following (in case it helps anyone):
1. Check the configuration of the autoProcessTV.cfg file (be sure there are no special characters and that you have entered the proper configuration otherwise)
2. Restart Sickbeard/SABnzbd
3.

a. Remove the script folder in Config->Folders
b. Restart SABnzbd

4.

a. Stop SABnzbd.
b. Go to the "temporary download folder" and delete or rename the folder associated with the stuck job.
c. Restart SABnzbd.

5. Reboot the system
6. Use the -c command, but remember the implications

Sorry to have wasted anyone's time and thanks for all the great work on this tremendous project!

Left this out last time:
Configuration:
Version: SABnzbd 0.6.15
OS: Ubuntu 11.11
Install type: Python source
Skin: Plush
Firewall software: None
IPV6? No
Reproducible? We'll have to see...

[abeam89]

Well I thought I'd let everyone know it happened again. However, I think I have more information that might help determine what might be causing this. I noticed some similarities in the symptoms/behaviors from the last time. I recall seeing two instances of SAB running the last time this happened, and that happened again. Before, I didn't think a whole lot of it because I had been restarting and everything so many different ways. This time, though, I noticed there were two instances before I did anything. So if that's part of the problem that would make a lot of sense.

Trying to shutdown SAB via any method was not working. I tried the web GUI, the api (init.d script), then attempted to kill the services manually. I didn't want to kill -9 and do any damage, so I just rebooted again.

Again, the reboot resolved the problem. I'm really not sure what's getting hung that is making this happen, but the behavior is really frustrating.

One difference this time is SAB didn't get hung (or at least didn't say it got hung) on the Sickbeard script. This time the web GUI showed it was attempting to unpack something (stopped at 25/25). There were quite a few other jobs which had already been downloaded that were waiting and there were still jobs in the queue as well. SAB was stuck there for at least 7 hours based on the successful post-processing completions prior to that.

I don't know if this helps any, but please let me know if I can provide any additional information to help.

Thanks again for all the tremendous work!

Configuration:
Version: SABnzbd 0.6.15
OS: Ubuntu 11.11
Install type: Python source
Skin: Plush
Firewall software: None
IPV6? No
Reproducible? We'll have to see...

[icki]

Hi
im in the same boat here.
today tried to download a bunch of files.
then it stuck without any usefull debuge information.

i checked HTOP and found 3 Instances of the Sabnzbddeamon running.

also i found that other tools had a similiar issue.(couchpotato)

if you find anything or the devs need more information im happy to provide


rgds
IckI

[shypike]

SABnzbd doesn't spontaneously start running multiple instances of itself.
Something else must have started these.
SABnzbd isn't designed to have multiple instances running, unless you use different ports
AND completely separate INI files, admin folder and "incomplete" folder and watched folder.

There is a detection mechanism in SABnzbd to prevent running multiple instances,
however effectivity varies per platform.
Windows is fine, due to using the registry to register a running instance.
OSX and Linux will check through the API for the same port being occupied.
When the designated port is free, it will start up, but will not check if there are overlapping admin folders.
(This check is hard to do without later getting problems with improperly terminated instances).

[tladd]

So im pretty new to all this but i was having some issues and found myself here with this one. I found a temp solution if you are NOT wanting to restart your pc at the moment this will get you by.

Withing sickbeard select manual post processing.
navigate to your sabnzb "complete folder" this will be where ever you set it. and press the process button.

for me it will push the pending file through and begin to unpack the next in queue
of course it sticks again at script. But helps if you are doing other things and are unwilling to restart.

[tladd]

found answer here which involves editing your ssl value in your script file

http://forums.sabnzbd.org/viewtopic.php?t=10801