Installing SickRage

[x219c]

Yeah, I'm not able to turn it on. I can SSH in, but it wouldn't let me start the service (though, maybe I have the wrong name)

[Mhynlo]

So you are starting the service as follows:

systemctl start fvapp-sickrage.service

If you are having issues, then you would want to look at the log output:

systemctl status fvapp-sickrage.service

-or-

journalctl -a --no-page _SYSTEMD_UNIT=fvapp-sickrage.service

I have seen a case where there is a PID that is created that systemd was not aware of. (I would need to look into that; interested if you are encountering this same issue.)

[x219c]

I think I was just doing this... But I will give that a try. I imagine that should work.

service sickrage start

[Mhynlo]

The ReadyNAS like systemd things, so that is why the service start looks a little different. (and the app requirement is to prepend the app with "fvapp-")

[x219c]

systemctl start fvapp-sickrage.service
Job failed. See system journal and 'systemctl status' for details.
root@Hydra:~# systemctl status fvapp-sickrage.service
fvapp-sickrage.service - Service for sickrage app
	  Loaded: loaded (/lib/systemd/system/fvapp-sickrage.service; enabled)
	  Active: inactive (dead) (Result: exit-code) since Tue, 29 Mar 2016 20:31:38 -0500; 11s ago
	 Process: 3996 ExecStart=/usr/bin/python /apps/sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/apps/sickrage/app-config --config=/apps/sickrage/app-config/config.ini --pidfile=/var/run/sickrage.pid (code=exited, status=1/FAILURE)
	Main PID: 5713 (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/fvapp-sickrage.service

root@Hydra:~# journalctl -a --no-page _SYSTEMD_UNIT=fvapp-sickrage.service
Logs begin at Sat, 26 Mar 2016 02:11:41 -0500, end at Sun, 27 Mar 2016 02:34:44 -0500.
Mar 27 22:56:30 Hydra python[9085]: PID file: /apps/sickrage/app-config/sickrage.pid already exists. Exiting.
Mar 27 22:56:31 Hydra python[9096]: PID file: /apps/sickrage/app-config/sickrage.pid already exists. Exiting.
Mar 27 22:56:31 Hydra python[9113]: PID file: /apps/sickrage/app-config/sickrage.pid already exists. Exiting.
Mar 27 22:56:32 Hydra python[9125]: PID file: /apps/sickrage/app-config/sickrage.pid already exists. Exiting.
Mar 27 22:56:32 Hydra python[9135]: PID file: /apps/sickrage/app-config/sickrage.pid already exists. Exiting.
Mar 27 22:56:33 Hydra python[9145]: PID file: /apps/sickrage/app-config/sickrage.pid already exists. Exiting.
Mar 28 21:00:22 Hydra python[5721]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 21:00:23 Hydra python[5731]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 21:00:23 Hydra python[5740]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 21:00:24 Hydra python[5749]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 21:00:24 Hydra python[5758]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:19:07 Hydra python[13689]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:19:07 Hydra python[13701]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:19:08 Hydra python[13711]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:19:08 Hydra python[13721]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:19:09 Hydra python[13731]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:19:10 Hydra python[13742]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:26:50 Hydra python[14540]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:26:50 Hydra python[14550]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:26:51 Hydra python[14560]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:26:52 Hydra python[14570]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:26:52 Hydra python[14581]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 28 22:26:53 Hydra python[14592]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 29 20:31:35 Hydra python[3926]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 29 20:31:36 Hydra python[3939]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 29 20:31:36 Hydra python[3949]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 29 20:31:37 Hydra python[3971]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 29 20:31:38 Hydra python[3984]: PID file: /var/run/sickrage.pid already exists. Exiting.
Mar 29 20:31:38 Hydra python[3996]: PID file: /var/run/sickrage.pid already exists. Exiting.

[Mhynlo]

That's what I am running into!

Mar 29 20:31:38 Hydra python[3996]: PID file: /var/run/sickrage.pid already exists. Exiting.

I am trying to figure out how the restart mechanic works with systemd.

I would check to see if it is running before doing deleting the pid file... (Note: Make sure that sickrage is not running before removing the file.)

ps aux | grep sickrage

(Make sure sickrage is not running.)

If it is indeed not running, then you could remove the file that "already exists".

rm /var/run/sickrage.pid

[x219c]

So, that worked. I tried the first command and didn't know if it was running from that... Then tried stopping it before pushing on. It's now up and running.

root@Hydra:~# ps aux | grep sickrage
root     10090  0.0  0.0  13152   692 pts/0    S+   21:30   0:00 grep sickrage
root@Hydra:~# systemctl stop fvapp-sickrage.service
root@Hydra:~# ps aux | grep sickrage
root     10234  0.0  0.0  13152   736 pts/0    S+   21:32   0:00 grep sickrage
root@Hydra:~# rm /var/run/sickrage.pid
root@Hydra:~# systemctl start fvapp-sickrage.service

[x219c]

If there's anything I can do to help you troubleshoot, (since my machine seems to have the same issue) let me know! 

[Mhynlo]

There was something in my systemd configuration that was a little agressive. I am going to do a quick check before committing and posting another release.

I will update here once that is posted.

[Mhynlo]

I uploaded the packed with the fix on github.

I was not able to get the configuration to allow the "shutdown" of the service within SickRage, but I was able to get the restarts/updates to work correctly.

Did you want to give it a go and let me know how it runs for you? (The initial checks that I ran appear to be running better.) 🙂

https://github.com/Mhynlo/rn-sickrage/releases/tag/2016.03.28-2

[pdid1]

I intend to start using this next week. I had been using the non echelon branch without issue for the past few months but, after messing around with logitech media server, I've broken something and had to do a soft reset. This has removed sickrage and I'm unable to install any apps either via ssh or through the frontend.

I will be doing a full factory reset and rebuild over the weekend and using your sickrage rather than trying to remember how I managed to install it last time! I'm a  linux novice but gained some useful knowledge working with raspberry pi's over the last few years.

So this is just a quick note to say thanks for adding this and I hope it works out well!

Cheers

[x219c]

Just downloaded and installed the new version. Ran an update and everything went perfect! Looking good so far! I don't shut down the NAS often, but the next time I do I'll update you. That appeared to be when I ran into the most problems...

It's worth noting that I got the same error after updating plex the other day. (NML) I had updated and immediately tried starting it, then I git the error. After waiting a minute (and doing nothing else) it started right up... Who knows, maybe it's firmware related or something.

[pdid1]

I'm running this now and mostly working ok. One problem I'm running into is for files that download that aren't in a folder eg:

2016-04-20 20:04:05 Thread-15 :: [/data/Transmission/Downloads/Line.Of.Duty.S01E01.HDTV.Subtitulado.Esp.SC.avi : Processing failed: File is locked for reading/writing]

 And another is not being able to delete the folder once processed eg:

2016-04-20 20:10:55 Thread-14 :: Warning: unable to delete folder: /data/Transmission/Downloads/Gotham.S02E18.720p.HDTV.X264-DIMENSION[rarbg]: error 13 : Permission denied

I'm assuming this must be something to do with ownership and permissions, any ideas? 

[Mhynlo]

Sickrage runs as admin so there should not be a permission issue. I have seen some cases where the torrent file would be locked, so when the file was locked from the torrent application it was not able to move the file.

Are you running a move post-process?

[pdid1]

Thanks for that, maybe the error is caused by Transmission? I'll have another look at the settings but I've only added username and passord so that shouldn't be an issue. I think I've worked around it by having an extra folder in the file structure but it is only a work around.

And yes it's a Move post process. Thanks

[Bogus]

You could try changing the umask setting in settings.json from 18 to 0:

"umask": 18,

becomes

"umask": 0,

(if umask is the last setting in settings.json then of course, there's no need for the comma at the end)

[pdid1]

I'll give that a try. Thanks

[pdid1]

I've run with the umask 0 setting for a few days now, unfortunately i'm still experiencing the same problem. I'll go back to the extra folder workaround for now. Cheers

[Dave_Ams]

All,

After stupidly deleting everything in my /usr/bin dir (trying to remove just a couple of symlinks but adding a space before the *, Duhhh) I had to do a re-install of RNOS 6.5. So far so good, I then tried to run NZBget and Sickrage, not surprisingly they didn't function, so re-installed the apps, NZBget works fine but SickRage wouldn't start.

Looking at the thread above I found the issue by looking at the log and saw that Python wasn't installed. Removed SickRage and reinstalled again, still no luck.

I used #apt-get install python it first said it was already there, fine, so apt-get remove python and re-install.

However SickRage still wouldn't run so I installed it on my second ReadyNAS Pro and compared the /usr/bin dirs and noticed that I still don't have a complete Python install as there are two files missing in /usr/bin

-rwxr-xr-x 1 root root 2663960 Jan 26 2013 python2.6

-rwxr-xr-x 1 root root 2884984 Mar 13 2014 python2.7

The symlinks were missing too but those I created myself

lrwxrwxrwx 1 root root 23 May 24 23:14 pdb2.6 -> ../lib/python2.6/pdb.py

lrwxrwxrwx 1 root root 23 May 24 23:14 pdb2.7 -> ../lib/python2.7/pdb.py

lrwxrwxrwx 1 root root 9 May 24 23:15 python -> python2.7

lrwxrwxrwx 1 root root 9 May 24 23:15 python2 -> python2.7

lrwxrwxrwx 1 root root 29 May 24 23:16 pyversions -> ../share/python/pyversions.py

Unsurprisingly the error is:

root@penguin-nas-1:/usr/bin# systemctl status fvapp-sickrage.service

fvapp-sickrage.service - Service for sickrage app

               Loaded: loaded (/lib/systemd/system/fvapp-sickrage.service; enabled)

               Active: inactive (dead)

               CGroup: name=systemd:/system/fvapp-sickrage.service

May 24 23:28:36 penguin-nas-1 systemd[28572]: Failed at step EXEC spawning /usr/bin/python: No such file or directory

Any ideas on how to force SickRage to install all it's dependencies?

David

[Dave_Ams]

All,

I ended up just copying the two files across, now SickRage works.

David

[jhagg]

I am running into this problem as well, SickRage cannot delete the Transmission file folders post process using move.  Not a show stopper but annoying, any help to solve this is apprecaited.