flokason Posted June 20, 2018 Share Posted June 20, 2018 Last Wednesday (13th of june) I noticed that my shows weren't automatically showing up in Plex So I checked the SABnzbd and saw this error: Quote Loading config from /config/autoProcessTV/autoProcessTV.cfg Opening URL: http://192.168.1.132:8082/home/postprocess/processEpisode?nzbName=Legion.S02E11.720p.HDTV.x264-AVS-Obfuscated.nzb&quiet=1&dir=%2Fdata%2Fcomplete%2FLegion+S02E11+720p+HDTV+x264-AVS-Obfuscated Unable to open URL: HTTP Error 500: Internal Server Error So the show is downloading, but it is not moving from the download file to the final destination Everything should be uptodate at my server Unraid 6.5.3 c/p from sickrage: SickRage Info: Quote Branch: master Commit: Database Version: 44.0 Python Version: 2.7.14 (default, Jan 5 2018, 10:41:29) [GCC 7.2.1 20171224] SSL Version: OpenSSL 1.1.0g 2 Nov 2017 OS: Linux-4.14.49-unRAID-x86_64-with-glibc2.2.5 According to the Docker section in unraid, everything is up-to-date I did not make any changes to the server what so ever, except I allow all the auto updating, both of the docker and unraid OS Anyone else has this problem? Quote Link to comment
Levente Posted June 22, 2018 Share Posted June 22, 2018 (edited) On 6/20/2018 at 10:20 AM, flokason said: Anyone else has this problem? Unfortunately I am having same issues as you. I think it started when I updated last time. Also binhex-sickrage exhibits same issues. Edited June 22, 2018 by Levente Quote Link to comment
graywolf Posted June 24, 2018 Share Posted June 24, 2018 On 6/20/2018 at 4:20 AM, flokason said: Last Wednesday (13th of june) I noticed that my shows weren't automatically showing up in Plex So I checked the SABnzbd and saw this error: So the show is downloading, but it is not moving from the download file to the final destination Everything should be uptodate at my server Unraid 6.5.3 c/p from sickrage: SickRage Info: According to the Docker section in unraid, everything is up-to-date I did not make any changes to the server what so ever, except I allow all the auto updating, both of the docker and unraid OS Anyone else has this problem? I'm having the same thing happen to me. Downloads but fails in post-processing. I have touch the config settings for sabnzb or sickrage in ages. Quote Link to comment
flokason Posted July 2, 2018 Share Posted July 2, 2018 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/ Quote Link to comment
saarg Posted July 2, 2018 Share Posted July 2, 2018 7 hours ago, flokason said: 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/ When it's fixed in the Sickrage repo, it will be in the next friday night (GMT) build. The fix is not merged yet into the sickrage repo, so you 'll have to wait. Quote Link to comment
xorinzor Posted September 20, 2018 Share Posted September 20, 2018 I'm having the issue where when I start my container, it somehow tries to run 2 servers, where 1 will run, and the other will endlessly restart, find that the port is already in use, stop, restart, etc. Did anyone else have this problem? if so, how did they resolve it? Quote Link to comment
Mefesto Posted October 12, 2018 Share Posted October 12, 2018 (edited) so, the TL;DR about what's happened is that https://github.com/SickRage/SickRage (origionally run by miigotu) was taken over by Echelon who ran another fork of sickrage that had very few users because he would do things like try and charge people a fee to use it or embedding minning software into his version. just recently he filed a fradulent tradmark on the name sickrage and convinced github to hand over control of miigotu's fork to Echelon. miigotu's is now running his fork out of https://github.com/SickChill/SickChill I suggest checking out the issue tracker if you want to try and fix it yourself, hopefully the docker maintainer will be able to fix it. echelon now runs the https://github.com/SickRage/SickRage site and Sickrage.ca. I'd advise everyone to stay away from echelon's software. Edited October 12, 2018 by Mefesto Quote Link to comment
dockerPolice Posted October 12, 2018 Share Posted October 12, 2018 (edited) *** POST DELETED *** Edited October 13, 2018 by dockerPolice Quote Link to comment
xorinzor Posted October 12, 2018 Share Posted October 12, 2018 Wow, I'm glad you guys found this out. Really not happy about this and will be disabling this container on my server for the time being. Quote Link to comment
dockerPolice Posted October 13, 2018 Share Posted October 13, 2018 12 minutes ago, xorinzor said: Wow, I'm glad you guys found this out. Really not happy about this and will be disabling this container on my server for the time being. 31 minutes ago, Mefesto said: so, the TL;DR about what's happened is that https://github.com/SickRage/SickRage (origionally run by miigotu) was taken over by Echelon who ran another fork of sickrage that had very few users because he would do things like try and charge people a fee to use it or embedding minning software into his version. just recently he filed a fradulent tradmark on the name sickrage and convinced github to hand over control of miigotu's fork to Echelon. miigotu's is now running his fork out of https://github.com/SickChill/SickChill I suggest checking out the issue tracker if you want to try and fix it yourself, hopefully the docker maintainer will be able to fix it. echelon now runs the https://github.com/SickRage/SickRage site and Sickrage.ca. I'd advise everyone to stay away from echelon's software. No bitcoining in the app as per echel0n https://forums.sickrage.ca/t/bitcoin-mining-has-been-removed/43 Quote I’ve gone ahead and disabled the embedded bitcoin mining code in both the app and websites for SiCKRAGE, this was originally put in to help with running costs of SiCKRAGE but has caused more issues then it was worth with anti-virus scanners resulting in URL blocks, please be sure to update you’re copy of the app to have this take affect for you. Quote Link to comment
xorinzor Posted October 13, 2018 Share Posted October 13, 2018 He may have disabled it, but he's still not the original author of the project. Merely just someone trying to be. Just because the name happens to match doesn't mean this, or something similar, won't happen in the future. I'd like the change to SickChill as that's the software we were all originally using and is what we should keep using. Quote Link to comment
raun Posted October 14, 2018 Share Posted October 14, 2018 My log is being filled with these messages: AA 2018-10-13 20:42:17 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:16 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:15 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:14 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:13 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:12 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:11 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:10 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' anyone else seeing this? Quote Link to comment
sickb0y Posted October 14, 2018 Share Posted October 14, 2018 1 hour ago, raun said: My log is being filled with these messages: AA 2018-10-13 20:42:17 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:16 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:15 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:14 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:13 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:12 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:11 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' AA 2018-10-13 20:42:10 ERROR Could not open static file u'/app/sickrage/gui/slick/images/sickchill.png' anyone else seeing this? Mine has been doing the same since early morning today (10 AM PST) I ended up shutting it down for the moment. Best wait for the sickchill docker to become available or wait for a fix as the current one got high jack by a previous developer. Quote Link to comment
kal Posted November 12, 2018 Share Posted November 12, 2018 Still getting this unfort... Im gonna switch over to Medusa methinks Quote Link to comment
Recommended Posts
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.