[Support] binhex - SickChill


binhex

Recommended Posts

Overview: Support for Docker image arch-sickchill in the binhex repo.

Application: SickChillhttps://github.com/SickChill/SickChill

Docker Hub: https://hub.docker.com/r/binhex/arch-sickchill/

GitHub: https://github.com/binhex/arch-sickchill

 

If you appreciate my work, then please consider buying me a beer 😁

 

btn_donate_SM.gif&key=57f6b617e37a194c35

 

For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

  • Like 1
Link to comment
Anything special about Sickchill over Medusa?
 
thanks.
The two are similar in their appearance but have a different feature set. your best bet is to compare the features listed on the github repo for each application to see if there is anything of interest that may make you switch. personally I use Medusa and for me it works very well so I shall be sticking with Medusa for now

Sent from my SM-G935F using Tapatalk

Link to comment

Well got a shock this morning as woke up to pretty much everything deleted from my TV directory. I had SickRage running perfectly for months up until this recent drama so started afresh with SIckChill last night. Set it up with Sab last night and had it downloading shows ok. The only thing that wasn't working was moving completed downloads into the correct sub folder but was going to deal with that today. I'd ran Add Shows - Add Exisitng shows and the library was populated (and is still populated), but pretty much everything is not on the server any longer.

 

I haven't had to set up Sickx and Sab in a while so I must have made an incorrect setting somewhere. Any ideas where to look to see how this has happened?

Link to comment

Backed my config up from interface in SickRage, restored the same profile in SickChill and restarted the service.

Docker itself was the same settings, with just a tweak to the port number until I kill off SR completely.

Seems to have been a painless exercise, everything working as it should.

 

Edited by tjb_altf4
  • Like 1
Link to comment
2 minutes ago, tjb_altf4 said:

Backed my config up from interface in SickRage, restored the same profile in SickChill and restarted the service.

Docker itself was the same settings, with just a tweak to the port number until I kill off SR completely.

Seems to have been a painless exercise, everything working as it should.

 

thats how it should be tbh, the old sickrage (not current release) and sickchill are the same code, all ive done is created a new image based off the old one, point it at the renamed github repo, tweak the templates etc and voila back up and running.

 

 

Link to comment
  • 3 weeks later...
  • 2 months later...
  • 4 weeks later...
5 hours ago, JWMutant said:

I love the Docker.... however can I request you add VPN support to the docker. My government is blocking more and more sites every year.

if you currently use any of my other vpn dockers then you can simply use privoxy and point sickchill (and any others) at privoxy to give you an unfiltered connection, im afraid adding in vpn for this app is way overkill and wont be happening.

Link to comment
35 minutes ago, binhex said:

if you currently use any of my other vpn dockers then you can simply use privoxy and point sickchill (and any others) at privoxy to give you an unfiltered connection, im afraid adding in vpn for this app is way overkill and wont be happening.

I do use DelugeVPN so will have to look into this Privoxy thing.

Link to comment
  • 4 weeks later...
  • 5 months later...

Is it recommended to update sickchill in this docker through its own web interface? It gives me a notice on the top of the page for how many commits behind I am compared to the github repo, in the past I have clicked the 'Update Now' link it provides and everything has seemed to work fine. But recently the update doesn't seem to finish properly. I get a notification that it's backing up my config but then the web interface will sit for an hour and never refresh itself. The log makes it look like the update happens, I get messages that seem to indicate an update is happening and don't see any errors.

 

But when I restart the docker it tells me I'm the same 13 commits behind again. Any ideas?

 

2019-07-25 14:49:40,408 DEBG 'sickchill' stderr output:
14:49:40 INFO::ThreadPoolExecutor-0_11 :: Config backup in progress...

2019-07-25 14:49:45,019 DEBG 'sickchill' stderr output:
14:49:45 INFO::ThreadPoolExecutor-0_11 :: Config backup successful, updating...

2019-07-25 14:49:45,818 DEBG 'sickchill' stderr output:
14:49:45 INFO::ThreadPoolExecutor-0_11 :: Creating update folder /opt/sickchill/sr-update before extracting

2019-07-25 14:49:45,819 DEBG 'sickchill' stderr output:
14:49:45 INFO::ThreadPoolExecutor-0_11 :: Downloading update from http://github.com/SickChill/SickChill/tarball/master

2019-07-25 14:49:50,910 DEBG 'sickchill' stderr output:
14:49:50 INFO::ThreadPoolExecutor-0_11 :: Extracting file /opt/sickchill/sr-update/sr-update.tar

2019-07-25 14:49:52,982 DEBG 'sickchill' stderr output:
14:49:52 INFO::ThreadPoolExecutor-0_11 :: Deleting file /opt/sickchill/sr-update/sr-update.tar

2019-07-25 14:49:52,986 DEBG 'sickchill' stderr output:
14:49:52 INFO::ThreadPoolExecutor-0_11 :: Moving files from /opt/sickchill/sr-update/SickChill-SickChill-1ed3156 to /opt/sickchill

2019-07-25 14:49:55,878 DEBG 'sickchill' stderr output:
14:49:55 INFO::MAIN :: Starting SickChill [master] using '/config/config.ini'

2019-07-25 14:49:55,898 DEBG 'sickchill' stderr output:
14:49:55 INFO::TORNADO :: Starting SickChill on http://0.0.0.0:8081/

2019-07-25 14:49:55,899 DEBG 'sickchill' stderr output:
14:49:55 INFO::CHECKVERSION :: Checking for updates using SOURCE

2019-07-25 14:54:55,201 DEBG 'sickchill' stderr output:
14:54:55 INFO::POSTPROCESSOR :: Auto post processing task for /data/complete was added to the queue

2019-07-25 14:54:56,197 DEBG 'sickchill' stderr output:
14:54:56 INFO::POSTPROCESSOR-AUTO :: Beginning auto post processing task: /data/complete

2019-07-25 14:54:56,199 DEBG 'sickchill' stderr output:
14:54:56 INFO::POSTPROCESSOR-AUTO :: Processing /data/complete

2019-07-25 14:54:56,197 DEBG 'sickchill' stderr output:
14:54:56 INFO::POSTPROCESSOR-AUTO :: Beginning auto post processing task: /data/complete

2019-07-25 14:54:56,199 DEBG 'sickchill' stderr output:
14:54:56 INFO::POSTPROCESSOR-AUTO :: Processing /data/complete

2019-07-25 14:55:11,988 DEBG 'sickchill' stderr output:
14:55:11 INFO::POSTPROCESSOR-AUTO :: Successfully processed

2019-07-25 14:55:11,989 DEBG 'sickchill' stderr output:
14:55:11 INFO::POSTPROCESSOR-AUTO :: Auto post processing task for /data/complete completed

2019-07-25 14:59:55,532 DEBG 'sickchill' stderr output:
14:59:55 INFO::DAILYSEARCHER :: Searching for new released episodes ...

 

Link to comment

 

 

 

 

Is it recommended to update sickchill in this docker through its own web interface?

 

In a word, no, you should not do this for any docker containers, updates are done via the 'check for updates' button in the docker unraid web ui

 

Sent from my CLT-L09 using Tapatalk

 

 

 

 

 

Link to comment
2 hours ago, binhex said:

In a word, no, you should not do this for any docker containers, updates are done via the 'check for updates' button in the docker unraid web ui

 

Sent from my CLT-L09 using Tapatalk

 

 

 

 

 

Thanks, I didn't really think so. I'm not that worried about being on the bleeding edge for features or security, just a habit to make an "Update Now!" notice like that go away.

Edited by cthrumplu
bad quote syntax
Link to comment
  • 3 months later...

TVDB lookups are currently broken due to the migration of thetvdb.com.  To temporarily fix this problem until the master branch gets the patch, follow these steps:

 

*1st add your Github account and save in General Configuration> Advanced Settings> Github sub-section.

Then go into: General Configuration> Advanced Settings> Branch Version> Select develop> Checkout Branch (will restart)

Once it comes back up, TheTVDB lookups for new shows/episodes will work again, but no new artwork will be downloaded.  Hopefully once both get patched in the master branch, BinHex will have compiled the new update and then you'll need to switch back to master branch in the location above and then update via your standard update procedure on the Docker page within UnRAID.

Edited by chesh
Link to comment
  • 4 months later...
  • 1 month later...
9 minutes ago, xtrips said:

Suddenly this morning Sickchill is blocked!

Hers is the message appearing on screen. 
What should I do? I tried the ini file in cache but I don't know how to proceed.
image.thumb.png.2b8c06ce8923a819da3a31d0ec452423.png
 

you either need to set a password for the web ui or stop port forwarding for this container on your router.

Link to comment
7 hours ago, binhex said:

you either need to set a password for the web ui or stop port forwarding for this container on your router.

Hello. I wish I could set a password. I just don't have access to the GUI yet.
And the port used by Sickchill is 8081 and is not forwarded in my router. 
What other option do I have?

 

Forget it! An update solved the problem apparently.

Edited by xtrips
Link to comment
  • 1 month later...

So I had to rebuild my docker environment this morning due to what appears to be a corrupt docker.img.  I was able to use all my templates and quickly brought everything back, however SickChill seems to have lost the ability to write files in the media directory.  I have done the chmod -R 777 in the target directory.  I can touch files with both the root and nobody account in this directory but it still fails to add new shows with the following as an example:

2020-07-17 13:01:53 WEBSERVER-ADDSHOWS :: [cddc3c8] Unable to create the folder /mnt/MAG_Pool/TV-Shows/Lost Speedways, can't add the show

 

Does anyone have any ideas?

Link to comment
  • 1 month later...

I updated last evening and tried to log in today, UI never shows and the log shows:

Quote

2020-09-06 13:32:58,725 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22829345373872 for <Subprocess at 22829345240976 with name sickchill in state STARTING> (stdout)>
2020-09-06 13:32:58,725 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22829345660736 for <Subprocess at 22829345240976 with name sickchill in state STARTING> (stderr)>
2020-09-06 13:32:58,726 INFO exited: sickchill (exit status 2; not expected)
2020-09-06 13:32:58,726 DEBG received SIGCHLD indicating a child quit
2020-09-06 13:33:01,733 INFO spawned: 'sickchill' with pid 61
2020-09-06 13:33:01,786 DEBG 'sickchill' stderr output:
/usr/sbin/python2: can't open file '/opt/sickchill/SickBeard.py': [Errno 2] No such file or directory

2020-09-06 13:33:01,787 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22829345241696 for <Subprocess at 22829345240976 with name sickchill in state STARTING> (stdout)>
2020-09-06 13:33:01,787 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22829344995168 for <Subprocess at 22829345240976 with name sickchill in state STARTING> (stderr)>
2020-09-06 13:33:01,788 INFO exited: sickchill (exit status 2; not expected)
2020-09-06 13:33:01,788 DEBG received SIGCHLD indicating a child quit
2020-09-06 13:33:02,789 INFO gave up: sickchill entered FATAL state, too many start retries too quickly

Looking at the github it looks like they might have upgraded to requiring Python3.X on their end. Is there a fix for this?

 

Thanks!

Link to comment

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.