[Support] binhex - SickRage


171 posts in this topic Last Reply

Recommended Posts

There seems to be an issue with the current release in the way it grabs torrents from Jackett (can't find releases even if they are on the tracker + jackett).

If I roll back to an earlier build (v2018.03.10-1-01), the issue goes away and everything is working again.

 

Not sure if something unique to my setup, but I thought I'd mention it.

Link to post
  • Replies 170
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

There has been a DMCA done by echel0n (because he says its his code as had the first fork lol when its midgetspys and open source!) which is causing an error on the general tab   A wor

im not really sure why people are going through the hassle of switching to a potentially dodgy source for sickrage, in my experience sickrage is still working just fine (am i missing something here?),

i am considering decrementing this in CA in favour of sickchill (rebadged sickrage), as im reasonably confident nobody really wants to use the current sickrage code (aka echel0n's) right?, anybody got

Posted Images

There seems to be an issue with the current release in the way it grabs torrents from Jackett (can't find releases even if they are on the tracker + jackett).
If I roll back to an earlier build (v2018.03.10-1-01), the issue goes away and everything is working again.
 
Not sure if something unique to my setup, but I thought I'd mention it.
If you are 100% sure this is broken in the latest image then I would encourage you to post this as an issue on the sickrage github repo (see op for link).

Sent from my SM-G935F using Tapatalk

Link to post
5 minutes ago, Maticks said:

I don’t think dev in sick rage is being maintained anymore

 

this is not true, last github release of sickrage was only a few days ago.

Link to post

v2018.04.02-1was supposed to fix the issue, but it hasn't resolved the issue for me.
I've tested about 8 versions until I narrowed the exact version that broke Jackett snatching and left that info for the devs.

 

v2018.03.19-1 is the last working version.
Just to eliminate variables, is there anything on the docker build side that might have changed @binhex?

Link to post
9 minutes ago, tjb_altf4 said:

v2018.04.02-1was supposed to fix the issue, but it hasn't resolved the issue for me.
I've tested about 8 versions until I narrowed the exact version that broke Jackett snatching and left that info for the devs.

 

v2018.03.19-1 is the last working version.
Just to eliminate variables, is there anything on the docker build side that might have changed @binhex?

 

not that would affect jackett to/from sickrage communication, nope.

 

are you using the jackett ..../all/.... trick for the url or have you added each jackett index site individually to sickrage? 

Link to post
7 hours ago, tjb_altf4 said:

v2018.04.02-1was supposed to fix the issue, but it hasn't resolved the issue for me.

 

you sure that made it into a github "release" ? last i saw it was merged into dev branch?

Link to post
9 hours ago, tjb_altf4 said:

Its in the release notes

hmm ok, well i guess you raise a new github issue saying its still not fixed, provide as much logging as possible.

Link to post
  • 2 weeks later...
Just tested with v2018.04.08-1.
Seems to be resolved now, not sure if my testing was flawed against v2018.04.02-1, but in any case all sorted now
I've actually switched over to medusa, now using jackett 'all' with no issues

Sent from my SM-G935F using Tapatalk

Link to post
  • 2 weeks later...

After running the Fix Common Problems tool. I have this error:

 

**** Template URL for docker application binhex-sickrage is missing. ****   **** Template URL for docker application couchpotato is missing. ****

 

The Docker containers are running fine, so I'm not clear on how a template goes missing and how do I correct this?

Link to post
1 hour ago, Switchblade said:

After running the Fix Common Problems tool. I have this error:

 

**** Template URL for docker application binhex-sickrage is missing. ****   **** Template URL for docker application couchpotato is missing. ****

 

The Docker containers are running fine, so I'm not clear on how a template goes missing and how do I correct this?

Replied in your other thread

Link to post
  • 1 month later...

Has anyone else seen this issue since the last update?

 

Loading config from /config/autoProcessTV/autoProcessTV.cfg

Opening URL: http://192.168.2.118:8081/home/postprocess/processEpisode?nzbName=The.Sopranos.S05E02.Rat.Pack.1080p.BluRay.x264-BHD-4Planet.nzb&quiet=1&dir=%2Fdata%2Fcomplete%2FTV+Shows%2FThe+Sopranos+S05E02+Rat+Pack+1080p+BluRay+x264-BHD-4Planet
Unable to open URL: HTTP Error 500: Internal Server Error

 

Here is the autoProcessTV.cfg file looks like.

 

This is the error I am getting in SabNZB when running the autoprocess from sickrage.  Please let me know if you need anymore info.  Any help is appreciated.

 

for reference I'm using unraid 6.4.1

 

And these Dockers

 

binhex/arch-sabnzbd

 

binhex/arch-sickrage

 

 

sabToSickBeard.py

Link to post
  • 2 weeks later...
  • 1 month later...
On 7/10/2018 at 1:57 AM, DTB7 said:

Just following up on my issue, willing to pay for someones time if they help me troubleshoot.  Need my tv shows lol.

Seems there are a fix on the way.. clipped from other forum:

 

"From what I have "googled" this may have been fixed in the original Sickrage (that is, not the docker)

Any possibilities that it may be updated any time soon?

 

In this thread is a possible temp fix:

 

https://github.com/SickRage/SickRage/issues/4783

 

But it requires changing a line in webserv.py in the docker itself. I would rather not do that, hopefully we'll get an updated docker soon

 

Until then, manually adding them here works:

local:8082/home/postprocess/"

Link to post
  • 2 weeks later...

hi, after update the docker, i got this issue:

 

2018-09-14 10:34:45,159 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23076737844504 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stdout)>
2018-09-14 10:34:45,160 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23076738003816 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stderr)>
2018-09-14 10:34:45,160 INFO exited: sickrage (exit status 2; not expected)
2018-09-14 10:34:45,160 DEBG received SIGCLD indicating a child quit
2018-09-14 10:34:48,166 INFO spawned: 'sickrage' with pid 46
2018-09-14 10:34:48,185 DEBG 'sickrage' stderr output:
/usr/sbin/python2: can't open file '/opt/sickrage/SickBeard.py': [Errno 2] No such file or directory

2018-09-14 10:34:48,186 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23076737844504 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stdout)>
2018-09-14 10:34:48,186 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23076735362040 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stderr)>
2018-09-14 10:34:48,186 INFO exited: sickrage (exit status 2; not expected)
2018-09-14 10:34:48,186 DEBG received SIGCLD indicating a child quit
2018-09-14 10:34:48,187 INFO gave up: sickrage entered FATAL state, too many start retries too quickly

 

Link to post
hi, after update the docker, i got this issue:
 
2018-09-14 10:34:45,159 DEBG fd 8 closed, stopped monitoring  at 23076737846160 with name sickrage in state STARTING> (stdout)>2018-09-14 10:34:45,160 DEBG fd 10 closed, stopped monitoring  at 23076737846160 with name sickrage in state STARTING> (stderr)>2018-09-14 10:34:45,160 INFO exited: sickrage (exit status 2; not expected)2018-09-14 10:34:45,160 DEBG received SIGCLD indicating a child quit2018-09-14 10:34:48,166 INFO spawned: 'sickrage' with pid 462018-09-14 10:34:48,185 DEBG 'sickrage' stderr output:/usr/sbin/python2: can't open file '/opt/sickrage/SickBeard.py': [Errno 2] No such file or directory2018-09-14 10:34:48,186 DEBG fd 8 closed, stopped monitoring  at 23076737846160 with name sickrage in state STARTING> (stdout)>2018-09-14 10:34:48,186 DEBG fd 10 closed, stopped monitoring  at 23076737846160 with name sickrage in state STARTING> (stderr)>2018-09-14 10:34:48,186 INFO exited: sickrage (exit status 2; not expected)2018-09-14 10:34:48,186 DEBG received SIGCLD indicating a child quit2018-09-14 10:34:48,187 INFO gave up: sickrage entered FATAL state, too many start retries too quickly

 


Same with me as well.


Sent from my iPhone using Tapatalk
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.