Sickchill: Echelon destroyed my install (FreeNAS) - any help?

Created on 10 Oct 2018  ·  35Comments  ·  Source: SickChill/SickChill

Before submitting your issue:

Sickrage webUI is completely broken.
My jail is running, networking is working, I can ping in / out of my jail.
I need to 'repair' my install of sickrage and get rid of this idiots code.
How do I go about doing this,
I do not have git installed in my FreeNAS jail, I don't know why? The plugin never needed it. I suppose I can pull it down in the meantime.

Most helpful comment

I've done something like this.

jls

to get the jail ID, 2 in my case

jexec 2 /bin/tcsh

to open a shell inside the jail
the service should be already stopped. otherwise

service sickrage stop

then

rm -r /usr/pbi/sickrage-amd64/share/sickrage/SickRage
fetch --no-verify-peer "https://github.com/SickChill/SickChill/archive/master.zip"
unzip master.zip
mv SickChill-master /usr/pbi/sickrage-amd64/share/sickrage/SickRage
chown -R media:media /usr/pbi/sickrage-amd64/share/sickrage/SickRage
rm master.zip
service sickrage start

Probably a change of git_remote_url to https://github.com/SickChill/SickChill.git in /var/db/sickrage/config.ini (always inside the jail) is needed for future updates.
This has brought my installation back to life.
However I don't know if it is the right way to fix this.

All 35 comments

I'm in the exact same boat. You're not alone. The plugin obviously doesn't use git so we're stuck on how to fix this.

Someone please help us on this, you're going on get a lot of people with this issue soon.

The temporary solution in #5022 should get you going again. We're terribly sorry this happened to you, please be patient as we find a solution.

It doesn't because we don't have git. The FreeNAS plugins don't use it.

On Wed., 10 Oct. 2018, 21:58 WebSpider, notifications@github.com wrote:

The solution in #5022 https://github.com/Sick-Rage/Sick-Rage/issues/5022
should get you going again. We're terribly sorry this happened to you,
please be patient as we find a solution.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Sick-Rage/Sick-Rage/issues/5026#issuecomment-428493696,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOjRRnZZZGND6Rc0lE_NUQ7toZlslJ8sks5ujbbLgaJpZM4XUkZj
.

Then we would need the maintainer of the FreeNAS plugin, if anyone knows who that is, a mention would be nice
(im returning to the project after at least 1.5 years of being busy with private and work matters ;-) )

I don't care if all I have to do is install git but surely there's another way to repair the files?

Try this:
Re-install
Don't update on first run
Stop it
Edit config.ini
Replace "git_remote_url = https://github.com/SickRage/SickRage.git"
with "git_remote_url = https://github.com/SickChill/SickChill.git "
Restart
Update

git_remote_url = https://github.com/SickChill/SickChill.git works better (in case the redirect stops working

Edited

"[EFAULT] An error occured! Please read above"

So the plugin is probably still pointing to the bad git repository, so we can't install a fresh copy without it being terrible unfortunately. So it'd be best if we simply repair the damaged one.

Do you need more information? I can post logs, or are just screwed without git to pull down fixed files?
Can we swear here? Cause fuck this echelon loser, fuck him and fuck his build, I'll NEVER switch to his shit copy and I'll make sure no one I know does.

Loser.

I guess you could probably use the zip to fix this up?

Can we please try and follow Github's community guidelines and avoid swearing, etc. we're above that. There's no reason to stoop back down to that level.

No problem. I think my opinion on the guy is pretty clear at this point

I'll try the zip, thank you.

(You wouldn't know the precise path to extract that, would you?)

Try this:
Re-install (from the sickchill.zip)
Don't update on first run
Stop it
Edit config.ini
Replace "git_remote_url = https://github.com/SickRage/SickRage.git"
with "git_remote_url = https://github.com/SickChill/SickChill.git "
Restart
Update

I followed these steps, and it still fails.

I am noticing a sickbeard.py and a sickrage.py after the update occurs, but the app won't restart. Manually starting either py just ends in a dos box flasking (I'm on Windows)

@phreaq we would need some logfiles to see what's going on in your install.

Here’s some log info (and some more background.

First, I’ve downloaded the sickchill.zip, and extracted it to a local drive.
I launch sickbeard.py, and the web page opens.
I then shut down sickchill, and edit the config.ini file to “git_remote_url = https://github.com/SickChill/SickChill.git
Relaunch sickbeard.py, web page opens, update… sickchill doesn’t reopen

2018-10-10 10:12:14 INFO CHECKVERSION :: Checking for updates using SOURCE
2018-10-10 10:12:50 INFO ThreadPoolExecutor-0_3 :: Config backup in progress...
2018-10-10 10:12:50 INFO ThreadPoolExecutor-0_3 :: Config backup successful, updating...
2018-10-10 10:12:51 INFO ThreadPoolExecutor-0_3 :: Creating update folder C:\Apps\SickChill\sr-update before extracting
2018-10-10 10:12:51 INFO ThreadPoolExecutor-0_3 :: Downloading update from http://github.com/SickRage/SickRage/tarball/master
2018-10-10 10:12:57 INFO ThreadPoolExecutor-0_3 :: Extracting file C:\Apps\SickChill\sr-update\sr-update.tar
2018-10-10 10:13:04 INFO ThreadPoolExecutor-0_3 :: Deleting file C:\Apps\SickChill\sr-update\sr-update.tar
2018-10-10 10:13:04 INFO ThreadPoolExecutor-0_3 :: Moving files from C:\Apps\SickChill\sr-update\SiCKRAGE-SiCKRAGE-ea0e19e to C:\Apps\SickChill

The logs are still pointing to the other build, but the config.ini still shows sickchill. Not sure where that's coming from...

Then we would need the maintainer of the FreeNAS plugin, if anyone knows who that is, a mention would be nice
(im returning to the project after at least 1.5 years of being busy with private and work matters ;-) )

https://github.com/freenas/iocage-ix-plugins/blob/master/sickrage.json.

Class action lawsuit against echel0n?

I think it would be a good idea for the owner of this fork to make a statement about what happen really, because personally I had auto update on, and now I don't know if my server is compromise or not.

From what I understand, the guy who took the original repo he's now able to send any files to anybody who still didn't notice the message on the web ui?

Please tell me I don't have to wipe my entire system because of this nonsense?

Any updates to this? My install is completely broken from this.

@Pbroc the reason he can still send updates to users is because Github allowed him to take over Sickrage/Sickrage. 😞

I've done something like this.

jls

to get the jail ID, 2 in my case

jexec 2 /bin/tcsh

to open a shell inside the jail
the service should be already stopped. otherwise

service sickrage stop

then

rm -r /usr/pbi/sickrage-amd64/share/sickrage/SickRage
fetch --no-verify-peer "https://github.com/SickChill/SickChill/archive/master.zip"
unzip master.zip
mv SickChill-master /usr/pbi/sickrage-amd64/share/sickrage/SickRage
chown -R media:media /usr/pbi/sickrage-amd64/share/sickrage/SickRage
rm master.zip
service sickrage start

Probably a change of git_remote_url to https://github.com/SickChill/SickChill.git in /var/db/sickrage/config.ini (always inside the jail) is needed for future updates.
This has brought my installation back to life.
However I don't know if it is the right way to fix this.

@mrktt thank God! You fixed it, you legend. My install is now up and running.

Now to turn off updates and do a configuration backup!

Thank you, dude.

Thanks @mrktt . That worked.
It's nice to have sickrage running again.

I did try updating within the gui after setting git_remote_url to https://github.com/SickChill/SickChill.git in /var/db/sickrage/config.ini. For some reason, sickrage crashed again. I just manually reinstalled to fix.

@trenst I think that the freenas plugin doesn't really use git_remote_url. This morning my installation, despite having changed the link to sickchill, tried to update again from the old url. Probably what yours had done. So for the moment I'm going to simply download the master.zip from time to time until every reference to the old site is removed or the plugin itself is updated to use sickchill.

@mrktt Can confirm, upgrading from master.zip until resolved.

@mrktt Thank you!

Guys, girls,

I'm on holiday unfortunately.

Can I confirm there's a single simple fix now?

Yes.

On Sun., 14 Oct. 2018, 20:36 jaxjexjox, notifications@github.com wrote:

Guys, girls,

I'm on holiday unfortunately.

Can I confirm there's a single simple fix now?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SickChill/SickChill/issues/5026#issuecomment-429603615,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOjRRrAlXZVHUi43xkgJomQGhc8aG5pOks5ukullgaJpZM4XUkZj
.

I've done something like this.

jls

to get the jail ID, 2 in my case

jexec 2 /bin/tcsh

to open a shell inside the jail
the service should be already stopped. otherwise

service sickrage stop

then

rm -r /usr/pbi/sickrage-amd64/share/sickrage/SickRage
fetch --no-verify-peer "https://github.com/SickChill/SickChill/archive/master.zip"
unzip master.zip
mv SickChill-master /usr/pbi/sickrage-amd64/share/sickrage/SickRage
chown -R media:media /usr/pbi/sickrage-amd64/share/sickrage/SickRage
rm master.zip
service sickrage start

Probably a change of git_remote_url to https://github.com/SickChill/SickChill.git in /var/db/sickrage/config.ini (always inside the jail) is needed for future updates.
This has brought my installation back to life.
However I don't know if it is the right way to fix this.

This did it for me aswell. Make sure you change to owner media:media or you can't update afterwards. I somehow missed that.

Just wanted to thank whomever released that master.zip file.

I have an iocage, new 11.2 jail (migrated from warden) and this still fixed me up.

Running 11.2/iocage plugin. My fix from jail:

service sickrage stop   # probably already down if you hit update, since it's borked
cd /usr/local/
pkg install git
git clone https://github.com/SickChill/SickChill.git
mv sickrage sickrage_old ; mv SickChill sickrage
chown -R sickrage:sickrage sickrage
cd sickrage_old
cp -R backup cache* config.ini failed.db Logs sickrage.db* ../sickrage
sed -ie 's/SickRage\/SickRage.git/SickChill\/SickChill.git/g' ../sickrage/config.ini 
service sickrage restart

thank you thank you thank you

I can confirm that @mrktt solution works for me as well (on Freenas)
There is one slight difference, which is the chmod command. My group and owner are different.
Thank you :)

This seems to be solved for everyone, closing issue

Was this page helpful?
0 / 5 - 0 ratings

Related issues

heymoe picture heymoe  ·  4Comments

d9001089 picture d9001089  ·  4Comments

Theli93 picture Theli93  ·  3Comments

mofman picture mofman  ·  4Comments

dilruwan7 picture dilruwan7  ·  3Comments