Page 1 of 1
sabtosickbeard.exe
Posted: April 1st, 2013, 2:40 pm
by baazil1
So I am using the sickbeard post-processing script in the autoprocesstv folder under the sickbeard directory... this has worked flawlessly in the past, but today, when I added my Tweaknews account info, it seems to be failing. Instead of processing in a matter of moments... its just stuck on Processing folder...
I've checked the folder it is processing, all the rar files are present. I cannot seem to get things to continue.
What happened? Any thoughts on why the script seems to be stuck?
Thanks!
Re: sabtosickbeard.exe
Posted: April 2nd, 2013, 10:08 pm
by gsharp
Newbie here and I'm having the same problem.
It looks like it downloads the show and I get the download symbol, the clock symbol, the unpack symbol, the wrench symbol and the view script log symbol.
When I double click on the script log symbol I can see this:
Loading config from C:\SickBeard\SickBeard-win32-alpha-build499\autoProcessTV\autoProcessTV.cfg
Opening URL:
http://localhost:8081/home/postprocess/ ... %5C***file***
Processing folder C:\Users\Gary\Documents\Downloads\complete\SABnzbd\***file***
and then it just sits there.
In the completed folder I see 4 files:
***file***.subs.sfv
***file***.NZB
***file***.idx
***file***.sub
Like I said I'm a newbie as I just got this working last week. Now I'm stuck again and looking to learn.
Version: (Ex: 0.7.11l)
OS: (Win 7)
Install-type: (Windows installer)
Skin (if applicable): (Default)
Firewall Software: (none)
Are you using IPV6? (no)
Is the issue reproducible? (yes)
Thanks!
Re: sabtosickbeard.exe
Posted: April 3rd, 2013, 12:13 pm
by shypike
Shouldn't you be asking this on the SickBeard forum?
Re: sabtosickbeard.exe
Posted: April 3rd, 2013, 12:37 pm
by gsharp
I'm not sure. I can't tell if it's having a problem on the SABnzbd side or the sick beard side.
I did notice that the original poster also posted on the sick beard forum so I'll watch that one too.
Re: sabtosickbeard.exe
Posted: April 3rd, 2013, 1:56 pm
by shypike
The question has been asked before and it always turned out to be some SickBeard setup issue.