On 9/14/2018 at 11:54 AM, binhex said:

im on it guys

thank you work again !

after last update got this error:

 

2018-10-09 11:43:01,479 INFO exited: sickrage (exit status 0; not expected)
2018-10-09 11:43:01,480 DEBG received SIGCLD indicating a child quit
2018-10-09 11:43:04,484 INFO spawned: 'sickrage' with pid 49
2018-10-09 11:43:04,572 DEBG 'sickrage' stderr output:
Traceback (most recent call last):
File "/opt/sickrage/sickrage/__init__.py", line 266, in main

2018-10-09 11:43:04,573 DEBG 'sickrage' stderr output:
from sickrage import core
File "/opt/sickrage/sickrage/core/__init__.py", line 34, in <module>
from apscheduler.schedulers.tornado import TornadoScheduler
ImportError: No module named apscheduler.schedulers.tornado

2018-10-09 11:43:04,576 DEBG 'sickrage' stdout output:
Failed to import required libs, please run 'pip install -r /opt/sickrage/requirements.txt' from console


2018-10-09 11:43:04,577 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22524775044376 for <Subprocess at 22524775046032 with name sickrage in state STARTING> (stdout)>
2018-10-09 11:43:04,577 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22524772561912 for <Subprocess at 22524775046032 with name sickrage in state STARTING> (stderr)>
2018-10-09 11:43:04,578 INFO exited: sickrage (exit status 0; not expected)
2018-10-09 11:43:04,578 DEBG received SIGCLD indicating a child quit
2018-10-09 11:43:05,580 INFO gave up: sickrage entered FATAL state, too many start retries too quickly

 

I updated today and now SR docker starts, but I cannot access the WUI, so this last update broke it.

 

You can roll back by changing latest to v2018.10.06-1-01 in your docker config for SickRage (full line should be: binhex/arch-sickrage:v2018.10.06-1-01).  You can watch here: https://hub.docker.com/r/binhex/arch-sickrage/builds/ for when binhex releases the next version that will fix the issue. Once a new release is out, change binhex/arch-sickrage:v2018.10.06-1-01 back to binhex/arch-sickrage:latest and it will grab the latest version.

Edited October 9, 20187 yr by chesh
Clarified what to change repository back to after new version comes out

 

I've never tried to roll back a docker before.  So to confirm, I just go to the console and type

binhex/arch-sickrage:v2018.10.06-1-01

 

And that will roll back SR?  I don't need to stop any service, or restart the server, nothing else?

 

Many thanks!

Edit the SickRage container and in the repository line change it binhex/arch-sickrage:latest to binhex/arch-sickrage:v2018.10.06-1-01 and hit save.  You'll have to manually remove the orphan from your docker tab. 

my repository line has this:  binhex/arch-sickrage

 

Yours has the word latest and then I see you point to a specific release.  I'm just curious why mine did not have the latest part at the end.  My install was  a fresh install of the binhex SR docker, with all defaults, and it has been working perfect until this last update blew it up.

 

I've never had to delete an orphan from docker tab either, so I need to read a little more before doing this.

 

Thanks!

 

Update:  ok, deleting orphan container is super easy, obvious which one to delete.  Changing the repository line worked great!  I'm back up and running again.

 

Thanks you again!

Edited October 9, 20187 yr by Switchblade

Not sure why yours doesn't have :latest.  Might be a carry over from an older version of unRaid (I've been using unRaid since 5.x). Deleting an orphan is as simple as clicking on the orphaned image and selecting delete (will be in the context menu). 

My SR install was fresh only a few months ago and it has prompted me to update several times since I've installed it.  I fully deleted my dockers at that time and recreated / installed everything fresh on a new cache drive.  In any case, now I know that trick so thanks again!

 

After a new working release comes out, I'll put mine to latest.

23 hours ago, ibasaw said:

after last update got this error:

 

2018-10-09 11:43:01,479 INFO exited: sickrage (exit status 0; not expected)
2018-10-09 11:43:01,480 DEBG received SIGCLD indicating a child quit
2018-10-09 11:43:04,484 INFO spawned: 'sickrage' with pid 49
2018-10-09 11:43:04,572 DEBG 'sickrage' stderr output:
Traceback (most recent call last):
File "/opt/sickrage/sickrage/__init__.py", line 266, in main

2018-10-09 11:43:04,573 DEBG 'sickrage' stderr output:
from sickrage import core
File "/opt/sickrage/sickrage/core/__init__.py", line 34, in <module>
from apscheduler.schedulers.tornado import TornadoScheduler
ImportError: No module named apscheduler.schedulers.tornado

2018-10-09 11:43:04,576 DEBG 'sickrage' stdout output:
Failed to import required libs, please run 'pip install -r /opt/sickrage/requirements.txt' from console


2018-10-09 11:43:04,577 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22524775044376 for <Subprocess at 22524775046032 with name sickrage in state STARTING> (stdout)>
2018-10-09 11:43:04,577 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22524772561912 for <Subprocess at 22524775046032 with name sickrage in state STARTING> (stderr)>
2018-10-09 11:43:04,578 INFO exited: sickrage (exit status 0; not expected)
2018-10-09 11:43:04,578 DEBG received SIGCLD indicating a child quit
2018-10-09 11:43:05,580 INFO gave up: sickrage entered FATAL state, too many start retries too quickly

 

i will see if i get time tonight to take a deeper look at the issue.

Thanks, binhex!

Quote

File "/opt/sickrage/sickrage/core/__init__.py", line 34, in <module>
from apscheduler.schedulers.tornado import TornadoScheduler
ImportError: No module named apscheduler.schedulers.tornado

receiving this error on 6.6.1

On 10/9/2018 at 6:12 PM, chesh said:

Edit the SickRage container and in the repository line change it binhex/arch-sickrage:latest to binhex/arch-sickrage:v2018.10.06-1-01 and hit save.  You'll have to manually remove the orphan from your docker tab. 

THANK YOU.  This at least got my docker up and running again until the current release gets sorted.

On 10/9/2018 at 10:54 AM, ibasaw said:

after last update got this error:

 

2018-10-09 11:43:01,479 INFO exited: sickrage (exit status 0; not expected)
2018-10-09 11:43:01,480 DEBG received SIGCLD indicating a child quit
2018-10-09 11:43:04,484 INFO spawned: 'sickrage' with pid 49
2018-10-09 11:43:04,572 DEBG 'sickrage' stderr output:
Traceback (most recent call last):
File "/opt/sickrage/sickrage/__init__.py", line 266, in main

2018-10-09 11:43:04,573 DEBG 'sickrage' stderr output:
from sickrage import core
File "/opt/sickrage/sickrage/core/__init__.py", line 34, in <module>
from apscheduler.schedulers.tornado import TornadoScheduler
ImportError: No module named apscheduler.schedulers.tornado

2018-10-09 11:43:04,576 DEBG 'sickrage' stdout output:
Failed to import required libs, please run 'pip install -r /opt/sickrage/requirements.txt' from console


2018-10-09 11:43:04,577 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22524775044376 for <Subprocess at 22524775046032 with name sickrage in state STARTING> (stdout)>
2018-10-09 11:43:04,577 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22524772561912 for <Subprocess at 22524775046032 with name sickrage in state STARTING> (stderr)>
2018-10-09 11:43:04,578 INFO exited: sickrage (exit status 0; not expected)
2018-10-09 11:43:04,578 DEBG received SIGCLD indicating a child quit
2018-10-09 11:43:05,580 INFO gave up: sickrage entered FATAL state, too many start retries too quickly

 

would like to +1 on this. rolling back worked and I am back up and running. Just letting you know it isn't an isolated event.

Not working since the update.

I will be more careful updating sickrage in the future.
Its the only docker that i have had these kind of problems with after updates.

Mine broke as well, thanks for the rolling-back advice!

READ THIS BEFORE RUNNING:- 

 

 

ok so after a bit of work on this i have fied it up, HOWEVER there has been a lot of chat regards sickrage and the fork now called sickchill, please be aware of the following notes shown on the sickchill github repo regards the current sickrage app:-

 

Quote

Please do not confuse us with SickRageTV aka Sickrage.ca.

We will never mine bit-coin on your machine, charge for a "service" or to use the software.

We also will never store your information, especially site logins to private trackers.

We believe in honesty and loyalty and privacy.

i personally dont want to get involved in this fight, but i wont be running sickrage on my system any time soon, i would recommend switching to sickchill (to be created) or the other very active fork called Medusa (check CA) but the choice is of course yours.

 

btw the issue building was caused by a bug in the girhub api and the release tag names, so for now the tag has had to be hard coded in (not good), this only affects the sickrage repo.

Edited October 14, 20187 yr by binhex

Thank you very much for the heads up. I wouldn't have known anything about this if you didn't say anything. I'm far to busy to keep up on the nitty gritty details of each of my Dockers. I'll be switching away from sickrage as well. Shame really, it's a wicked docker. 

 

Hopefully one of these other forks supports importing the backup configuration and database file from sickrage as I have a pretty massive list of shows in my sickrage currently. 

Just converted to Medusa w/ a backup/restore of configuration files.  Once you've done the restore in Medusa, go into appdata\binhex-medusa\restore and rename the .db file to main.db and then restart the container.  That was the only one off I had to do to get my DB restored.  After that, I just checked all my settings and corrected anything that didn't convert over correctly.  Shutdown and deleted Sickrage once I got that all fixed. Everything seems to be working well now.

SickChill is now available (renamed fork that was as far as you guys are concerned, sickrge) so it should be a drop in replacement once the container is configured the same way.

Sent from my SM-G935F using Tapatalk

FYI: Converting from Sickrage to Sickchill was extremely simple.  Take a backup of your configuration from before Saturday (10/13) and just restore it into Sickchill (should be in appdata\Sickrage\backup and is a .zip file).  If you don't have a backup in that location, do my trick above to switch back to the 10-6 version of Sickrage, don't start the container, rename all of the .old files in your configuration directory back to .db files and then start Sickrage.  From here you can go into Settings -> Backup/Restore and make a backup.  Then, shutdown Sickrage, start Sickchill, and restore your backup. Should be as easy as that.  I had previously gone to Medusa, but it uses slightly different tables in the .db file and not everything was working as nice as I would have liked (some shows were showing up in my shows list, but I couldn't access them from the dropdown and then Sickrage started redownloading all the episodes, even though I didn't have any missing episodes). If you do these instructions to switch to Sickchill, the worse you may have to deal with is it not knowing about all the episodes it has downloaded since the backup was made.  They'll just show up in your Schedule as missed episodes.  If you go into each show that is "missed" (but has already downloaded) you can just "Re-scan files" and it will find the file downloaded and not try to redownload it.   It may try to postprocess it again, but that won't harm anything other then move the episode to the front of Recently Added TV. 

I'll give that a try. I've been trying unsuccessfully for the past two days to migrate to sickchill or Medusa. 

 

With Medusa my added shows are showing all the downloaded episodes as archived for some reason and the post processing script won't work with it (even though I edited it with correct details for Medusa) 

 

With sickchill I was able to restore my entire library as well as settings with the restore feature but same deal, it won't play nicely with nzbtomedia post processing script. 

 

Getting fairly frustrated but I'll try the above and see where that gets me, then try and figure out why the f nzbtomedia won't work on either. 

 

Update: Managed to migrate over to medusa using chesh's pointers.  Thank you very much.  Post processing script also sorted. Medusa wasn't able to see my completed downloads folder, had to add a custom path on the docker for /downloads, after adding that its working again.  

Edited October 16, 20187 yr by Drezdun

Hello - hoping somebody can help. My Sickrage docker install has just updated into a new look Sickrage - seems to be working OK but getting the error message "Unable to find your pip executable - Set your pip path from Settings->General->Advanced"... can anyone advise re where to find/set this (ideally in simple beginerish terms please).... thanks in anticipation

1 hour ago, DavidJK said:

Hello - hoping somebody can help. My Sickrage docker install has just updated into a new look Sickrage - seems to be working OK but getting the error message "Unable to find your pip executable - Set your pip path from Settings->General->Advanced"... can anyone advise re where to find/set this (ideally in simple beginerish terms please).... thanks in anticipation

You can safely ignore the error.  It'll be fixed in an update to the container.  Read above if you want to know what's going on w/ Sickrage/Sickchill/Medusa

Really helpful - thank you very much - lots to think about re whether to stay as is or move over to Medusa .... kind of feels like my UnRaid box has been hijacked! Thanks again