Sickrage installation fails

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
cpp
Posts: 8
Joined: Wed Mar 15, 2017 1:39 pm

Sickrage installation fails

Post by cpp »

I did a fresh install to my RPi 3 b+ to be my server (previous was a RPi 3 running dietpi and several services just perfectly).

First install gives me some problems hanging on boot as using external partitions for /var but I resolved it using a symlink, all is fine but sickrage fails to install (details in a sec) and I think it's due to me moving the default dietpi_userdata location (through dietpi-drive-manager).

Today, as a test, I tried a fresh install onto another SD (on the same RPi) with no external HD, therefore everything is on the SD card.

Whilst installing sickrage, I notice it hangs a bit and complains saying it cannot find SickBeard.py in the /mnt/dietpi-userdata folder and therefore it cannot create its config.ini file, since it was installing I could not (or I don't know how) grab the output of the errors nor the ones on boot (dmesg | grep sickrage and similar greps give 0 results).

Following some outputs:

Code: Select all

root@DietPi:~# dietpi-services restart
[  OK  ] DietPi-Services | Root access verified.

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: restart

[  OK  ] DietPi-Services | restart : transmission-daemon
[FAILED] DietPi-Services | restart : sickrage
[  OK  ] DietPi-Services | restart : cron
[ SUB1 ] DietPi-Process_tool > Apply
[  OK  ] DietPi-Process_tool | Cron (1727) : Nice      0
[  OK  ] DietPi-Process_tool | Cron (1727) : Affinity  0-3
[  OK  ] DietPi-Process_tool | Cron (1727) : Scheduler SCHED_OTHER 0
[  OK  ] DietPi-Process_tool | DHCP Client (737) : Nice      0
[  OK  ] DietPi-Process_tool | DHCP Client (737) : Affinity  0-3
[  OK  ] DietPi-Process_tool | DHCP Client (737) : Scheduler SCHED_OTHER 0
[  OK  ] DietPi-Process_tool | Dropbear (270) : Nice      0
[  OK  ] DietPi-Process_tool | Dropbear (270) : Affinity  0-3
[  OK  ] DietPi-Process_tool | Dropbear (270) : Scheduler SCHED_OTHER 0
[  OK  ] DietPi-Process_tool | Dropbear (1177) : Nice      0
[  OK  ] DietPi-Process_tool | Dropbear (1177) : Affinity  0-3
[  OK  ] DietPi-Process_tool | Dropbear (1177) : Scheduler SCHED_OTHER 0
[  OK  ] DietPi-Process_tool | SickRage () : Nice      0
[FAILED] DietPi-Process_tool | SickRage () : Affinity  0-3
[  OK  ] DietPi-Process_tool | SickRage () : Scheduler SCHED_OTHER 0
[  OK  ] DietPi-Process_tool | Transmission (1704) : Nice      0
[  OK  ] DietPi-Process_tool | Transmission (1704) : Affinity  0-3
[  OK  ] DietPi-Process_tool | Transmission (1704) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | An issue has occurred

Code: Select all

root@DietPi:~# systemctl status sickrage.service 
● sickrage.service - SickRage
   Loaded: loaded (/etc/systemd/system/sickrage.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-10-20 14:57:36 BST; 24s ago
  Process: 1962 ExecStart=/usr/bin/python /mnt/dietpi_userdata/sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/mnt/dietpi_userdata/sickrage (code=exited, status=2)

Oct 20 14:57:36 DietPi systemd[1]: sickrage.service: Control process exited, code=exited status=2
Oct 20 14:57:36 DietPi systemd[1]: Failed to start SickRage.
Oct 20 14:57:36 DietPi systemd[1]: sickrage.service: Unit entered failed state.
Oct 20 14:57:36 DietPi systemd[1]: sickrage.service: Failed with result 'exit-code'.
Oct 20 14:57:36 DietPi systemd[1]: sickrage.service: Service hold-off time over, scheduling restart.
Oct 20 14:57:36 DietPi systemd[1]: Stopped SickRage.
Oct 20 14:57:36 DietPi systemd[1]: sickrage.service: Start request repeated too quickly.
Oct 20 14:57:36 DietPi systemd[1]: Failed to start SickRage.
Oct 20 14:57:36 DietPi systemd[1]: sickrage.service: Unit entered failed state.
Oct 20 14:57:36 DietPi systemd[1]: sickrage.service: Failed with result 'exit-code'.

Code: Select all

root@DietPi:~# dietpi-services restart sickrage.service
[  OK  ] DietPi-Services | Root access verified.

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: restart

[FAILED] DietPi-Services | restart sickrage.service

Code: Select all

root@DietPi:~# cat /var/log/syslog | grep sickrage
Oct 20 14:56:48 DietPi python[1135]: /usr/bin/python: can't open file '/mnt/dietpi_userdata/sickrage/SickBeard.py': [Errno 2] No such file or directory
Oct 20 14:56:48 DietPi systemd[1]: sickrage.service: Control process exited, code=exited status=2
Oct 20 14:56:48 DietPi systemd[1]: sickrage.service: Unit entered failed state.
Oct 20 14:56:48 DietPi systemd[1]: sickrage.service: Failed with result 'exit-code'.
Oct 20 14:56:49 DietPi systemd[1]: sickrage.service: Service hold-off time over, scheduling restart.

Code: Select all

root@DietPi:~# ls -l /mnt/dietpi_userdata/sickrage/
total 0
-rwxrwxr-x 1 sickrage dietpi 0 Oct 20 13:31 config.ini
root@DietPi:~# cat /mnt/dietpi_userdata/sickrage/config.ini 
root@DietPi:~# 
If anyone has a similar issue or knows the answer?
Is there furhter code I should post?

Thanks in advance
cpp
maheshrao
Posts: 1
Joined: Fri Sep 22, 2017 5:10 am

Re: Sickrage installation fails

Post by maheshrao »

i have the same issue.i tried to find the source of sickrage repo,but i cant it.Only one i can find is https://sickrage.ca/.I think the installation need to be modified for this new repo.
User avatar
MichaIng
Site Admin
Posts: 2423
Joined: Sat Nov 18, 2017 6:21 pm

Re: Sickrage installation fails

Post by MichaIng »

Jep this is a known issue since Sickrage renamed it's repo: https://github.com/Fourdee/DietPi/issues/2126

Please try it with the current beta: https://github.com/Fourdee/DietPi/issues/2140
cpp
Posts: 8
Joined: Wed Mar 15, 2017 1:39 pm

Re: Sickrage installation fails

Post by cpp »

After trying the beta and lately a fresh install of the new 6.17.12 sickrage seemed to work, I left few days and boom, it wasn't working (although dietpi said it was up and running).

After few attempts I uninstalled it and reinstalled it, few times, it ifnally was up and running, re-imported all my tv shows, updated everything, tested few hours wholst cleaning the ended shows and moving folders, in the end all worked, all tests fine....

This morning, again, it's there hanging, no response from the web interface and all I can see is this from htop:

Code: Select all

sickrage 0 99.0 2.6 0:05.48 /usr/bin/python /mnt/dietpi_userdata/sickrage/SICKRAGE.py -d --nolaunch --datadir=/mnt/dietpi_userdata/sickrage
and this from /mnt/dietpiuserdata/sickrage/logs/sickrage.log (show names manually removed ---)

Code: Select all


2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::260449: Saving show to database: ---
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::153021: Saving show to database: ---
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::296762: Saving show to database: ---
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::323168: Saving show to database: ---
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::333072: Saving show to database: ---
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::346328: Saving show to database: ---
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::292157: Saving show to database: --- 
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::Saving all settings to disk
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::Shutting down main database connection
2018-11-10 06:50:16 DEBUG::VERSIONUPDATER::Shutting down cache database connection


Any suggestions? Should I try a manual install of sickrage? is medusa a reliable option at this stage on dietpi?

btw: I'm on a RPi 3 b+
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

Re: Sickrage installation fails

Post by johnvick »

Medusa runs well on my XU4 but I'm still on DietPi 159 on that device.

John
User avatar
MichaIng
Site Admin
Posts: 2423
Joined: Sat Nov 18, 2017 6:21 pm

Re: Sickrage installation fails

Post by MichaIng »

Yeah it's a pain currently with Sickrage. They renamed their repo and changed install method, obviously under heavy development, meanwhile a fork SickChill was created and now I read that Mich devs switched to Medusa.

Will try to replicate, maybe we need to disable sickrage for a while, adding one or both alternatives instead.
User avatar
aermak
Posts: 1
Joined: Sun Nov 11, 2018 1:52 pm

Re: Sickrage installation fails

Post by aermak »

I'd kill Sickrage option altogether and make Sickchill or Medusa available instead. It's a pain having to go through all the mess when all you want is a stable system to get some content on your screen!

https://sickchill.github.io/
https://cdn.pymedusa.com/

reasons why:

https://www.reddit.com/r/synology/comme ... fects_you/
User avatar
MichaIng
Site Admin
Posts: 2423
Joined: Sat Nov 18, 2017 6:21 pm

Re: Sickrage installation fails

Post by MichaIng »

Thanks for the link/info. The case is clear then. We will enable SickChill quickly (since, AFAIK our old install method still works) and have a look at Meduse, most properly at a later stage to not further delay v6.18 release (which fixes some critical bugs).

Ref: https://github.com/Fourdee/DietPi/issues/2239
cpp
Posts: 8
Joined: Wed Mar 15, 2017 1:39 pm

Re: Sickrage installation fails

Post by cpp »

Good news, is there already a beta to test sickchill or an installation guide for raspbian/dietpi?

Thanks
User avatar
MichaIng
Site Admin
Posts: 2423
Joined: Sat Nov 18, 2017 6:21 pm

Re: Sickrage installation fails

Post by MichaIng »

Actually we decided to drop Sickrage/chill support for now due to fork and install method changes until it stabilized. We aim to implement Medusa as an alternative with v6.19.

But you can try official install instructions: https://github.com/SickChill/SickChill/ ... -Ubuntu-15
Post Reply