NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Installing SickRage
Hello
I'm trying to install SickRage using this guide: https://sickrage.tv/forums/forum/help-support/general-support/6013-sickrage-ubuntu-install-guide . It appears to be working, but stops as soon as I close the terminal window.
I've set the content of /etc/default/sickbeard to:
SB_USER=admin SB_HOME=/data/SickRage-src/ SB_DATA=/data/SickRage-src/ SB_OPTS=–config=/data/SickRage-src/config.ini
However I'm getting an error launching the service:
update-rc.d: using dependency based boot sequencing insserv: warning: script 'leafp2p' missing LSB tags and overrides
I tried google, but couldn't find any entries related to sickrage
45 Replies
Replies have been turned off for this discussion
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
All,
I ended up just copying the two files across, now SickRage works.
David
- I've always had transmission download to a different folder inside my media share. Not the transmission share. Then sickbeard watches there. Once it finishes downloading, it can move the files around because they're not going across shares.
Yes, that works indeed. Thanks!
This package is now available on the app site:
- No, I wish it was that simple. I checked that and made sure the torrent wasn't seeding anymore. Even manual post processing gave the same error. It can copy but not move.
Bogus wrote:
No, I wish it was that simple. I checked that and made sure the torrent wasn't seeding anymore. Even manual post processing gave the same error. It can copy but not move.Thanks for making the package. I'll try it out.
For transmission issues I've had that before. Are both sickrage and transmission installed on the data volume?
You could try changing the folder permissions using something like FILEZILLA.
- Transmission is by default installed in it's own share and downloads too in that share. When Sickrage tries to move the file from the Transmission share to the movie share, I receive an error that the file cannot be moved, because the file is locked.
Bogus wrote:
Transmission is by default installed in it's own share and downloads too in that share. When Sickrage tries to move the file from the Transmission share to the movie share, I receive an error that the file cannot be moved, because the file is locked.That is most likely because the file is still seeding when it is being moved.
it is normal.
I have a ReadyNas 312 with firmware 6.4.2.
Hello MaartenProvo,
I've moved your post from Using your ReadyNAS board to Community Add-ons board.
Like what Stephen said, it is best you contact the developer.
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
