SOLVED SickRage Not Starting/Running (Jruehlig Setup)

mh348

Dabbler
Joined
Oct 4, 2011
Messages
10
Hi, A while back I followed the guide by JRuehlig https://www.jruehlig.com/wordpress/installation-configuration-of-freenas-plugins/ [I have the site bookmarked, but there seems to be an issue with the site].

My setup was working 100% (thanks Joshua) until a week ago, but now for some reason, SickRage fails to open up on the web interface. I haven't made any changes, so I'm not sure what went wrong.

FreeNAS Version: FreeNAS-9.10.2-U6 (561f0d7a1)
SickRage Version: sickrage-autoupdate.9_1-amd64 (got the verison from the directory /mnt/tank/jails/sabnzbd_1/var/db/pbi/installed/sickrage-autoupdate.9_1-amd64/)
Port: 8081
Jail IP:192.168.10.1

The PBI that was installed it also from the Guide, (http://download.freenas.org/plugins/9/x64/sickrage-autoupdate.9_1-amd64.pbi)

All my other plugins still work 100% (Sab, Transmission, CP).

1. How do I check if SickRage is running?
2. How do I check logs to see if there is an error, preventing it from starting up?

I still consider myself a noob when it comes to Linux as everything I do is from guides.

When I run a port query from windows on port 8081, it shows that the port is closed. This might be because SickRage isn't running.

Code:
 Starting portqry.exe -n 192.168.10.1 -e 8081 -p TCP ...


Querying target system called:

 192.168.10.1

Attempting to resolve IP address to a name...

Failed to resolve IP address to name

querying...

TCP port 8081 (unknown service): NOT LISTENING
portqry.exe -n 192.168.10.1 -e 8081 -p TCP exits with return code 0x00000001.
 

mh348

Dabbler
Joined
Oct 4, 2011
Messages
10

Thanks! I found the solution there.

I did search the forum first, but somehow missed that thread..

For anyone else that has the same issue as me, I followed the instructions from Jruehlig on Switching from SickRage to SickChill,
https://forums.freenas.org/index.ph...rt-after-last-update.70477/page-3#post-488266

ssh into FreeNAS
Use the following command to locate jails:
Code:
jls


Then use the command to enter the jail:
Code:
jexec sabnzbd_1


Once in the jail, follow these steps.
Code:
service sickrage onestop
rm -r /usr/pbi/sickrage-amd64/share/sickrage/SickRage
fetch --no-verify-peer "https://github.com/SickChill/SickChill/archive/master.tar.gz"
tar -zxf master.tar.gz
mv SickChill-master /usr/pbi/sickrage-amd64/share/sickrage/SickRage
chown -R media:media /usr/pbi/sickrage-amd64/share/sickrage/SickRage
rm master.tar.gz
service sickrage start

Once complete, use the same SickRage port & url, and do an update from the web interface.
 

Maturola

Explorer
Joined
Jun 26, 2014
Messages
85
I just had this issues, trying this but i get the follwing error, any ideas?

Code:
root@sabnzbd_1:/ # fetch --no-verify-peer "https://github.com/SickChill/SickChill/archive/master.tar.gz"

68823:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c:585:

fetch: https://github.com/SickChill/SickChill/archive/master.tar.gz: Authentication error


I'm going to go check the other thread...

EDIT: I manually downloaded the file and SCP it to the Jail..
 
Last edited:

Maturola

Explorer
Joined
Jun 26, 2014
Messages
85
At least Sickrage is up, however I get this error, even after updating from the UI

Code:
Unknown current version number: If you've never used the SickRage upgrade system before then current version is not set.— Update Now


I don't see anything error on logs, however the http://0.0.0.0:8081 seems weird.

Code:
2018-11-15 10:30:45 INFO	 CHECKVERSION :: Checking for updates using SOURCE
2018-11-15 10:30:45 INFO	 TORNADO :: Starting SickRage on http://0.0.0.0:8081/
2018-11-15 10:30:45 INFO	 MAIN :: 301567: Unable to find IMDb show info in the database
2018-11-15 10:30:45 INFO	 MAIN :: Writing PID: 55156 to /var/run/sickrage/sickrage.pid
2018-11-15 10:30:41 INFO	 EVENT-QUEUE :: Restarting SickRage with ['/usr/pbi/sickrage-amd64/bin/python2.7', '/usr/pbi/sickrage-amd64/share/sickrage/SickRage/SickBeard.py', '--datadir', '/var/db/sickrage', '-d', '--pidfile', '/var/run/sickrage/sickrage.pid', '-q', '--nolaunch']
2018-11-15 10:30:41 INFO	 EVENT-QUEUE :: Shutting down Tornado
2018-11-15 10:30:41 INFO	 EVENT-QUEUE :: Saving config file to disk
2018-11-15 10:30:38 INFO	 EVENT-QUEUE :: Saving all shows to the database
2018-11-15 10:30:37 INFO	 EVENT-QUEUE :: Waiting for the SUBTITLESFINDER thread to exit
2018-11-15 10:30:37 INFO	 EVENT-QUEUE :: Waiting for the PROPERFINDER thread to exit
2018-11-15 10:30:36 INFO	 EVENT-QUEUE :: Waiting for the TRAKTCHECKER thread to exit
2018-11-15 10:30:35 INFO	 EVENT-QUEUE :: Waiting for the POSTPROCESSER thread to exit
2018-11-15 10:30:35 INFO	 EVENT-QUEUE :: Waiting for the SEARCHQUEUE thread to exit
2018-11-15 10:30:35 INFO	 EVENT-QUEUE :: Waiting for the SHOWQUEUE thread to exit
2018-11-15 10:30:34 INFO	 EVENT-QUEUE :: Waiting for the VERSIONCHECKER thread to exit
2018-11-15 10:30:34 INFO	 EVENT-QUEUE :: Waiting for the SHOWUPDATER thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Waiting for the BACKLOG thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Waiting for the DAILYSEARCH thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Waiting for the EVENTS thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Aborting all threads
2018-11-15 10:30:32 INFO	 Thread-62 :: Moving files from /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update/SiCKRAGE-SiCKRAGE-dd00ab8 to /usr/pbi/sickrage-amd64/share/sickrage/SickRage
2018-11-15 10:30:32 INFO	 Thread-62 :: Deleting file /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update/sr-update.tar
2018-11-15 10:30:32 INFO	 Thread-62 :: Extracting file /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update/sr-update.tar
2018-11-15 10:30:30 INFO	 Thread-62 :: Downloading update from 'http://github.com/SickRage/SickRage/tarball/master'
2018-11-15 10:30:30 INFO	 Thread-62 :: Creating update folder /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update before extracting
2018-11-15 10:30:30 INFO	 Thread-62 :: Config backup successful, updating...
2018-11-15 10:30:20 INFO	 Thread-62 :: Config backup in progress...
 
Last edited:

fontes31

Explorer
Joined
Apr 6, 2012
Messages
96
Hi, A while back I followed the guide by JRuehlig https://www.jruehlig.com/wordpress/installation-configuration-of-freenas-plugins/ [I have the site bookmarked, but there seems to be an issue with the site].

My setup was working 100% (thanks Joshua) until a week ago, but now for some reason, SickRage fails to open up on the web interface. I haven't made any changes, so I'm not sure what went wrong.

FreeNAS Version: FreeNAS-9.10.2-U6 (561f0d7a1)
SickRage Version: sickrage-autoupdate.9_1-amd64 (got the verison from the directory /mnt/tank/jails/sabnzbd_1/var/db/pbi/installed/sickrage-autoupdate.9_1-amd64/)
Port: 8081
Jail IP:192.168.10.1

The PBI that was installed it also from the Guide, (http://download.freenas.org/plugins/9/x64/sickrage-autoupdate.9_1-amd64.pbi)

All my other plugins still work 100% (Sab, Transmission, CP).

1. How do I check if SickRage is running?
2. How do I check logs to see if there is an error, preventing it from starting up?

I still consider myself a noob when it comes to Linux as everything I do is from guides.

When I run a port query from windows on port 8081, it shows that the port is closed. This might be because SickRage isn't running.

Code:
Starting portqry.exe -n 192.168.10.1 -e 8081 -p TCP ...


Querying target system called:

192.168.10.1

Attempting to resolve IP address to a name...

Failed to resolve IP address to name

querying...

TCP port 8081 (unknown service): NOT LISTENING
portqry.exe -n 192.168.10.1 -e 8081 -p TCP exits with return code 0x00000001.

Hi,
how can i have access to www.jruehlig.com/wordpress/installation-configuration-of-freenas-plugins/?

Thanks
 
Top