I’m running OSMC on a pi3 and Sickrage was working fine until last OSMC update. I’m not sure what causes it to stop but had no other change in my system other than the update.
When I type :
sudo service sickrage start
I get:
Job for sickrage.service failed because a timeout was exceeded.
See “systemctl status sickrage.service” and “journalctl -xe” for details.
From SSH, try running the same startup command as is run from /etc/systemd/system/sickrage.service. It’s on the ExecStart line. (You will probably need to logon as the sickrage user before running the command.)
I see you ran it with sudo, so it looks like it might be a permissions problem, since I think it normally runs under the user sickrage. You need to check in /etc/systemd/system/sickrage.service to see if that is correct. I don’t have it installed, so I’m guessing a bit.
As I said last time, you should also try to logon as the sickrage user and run the same command. Alternatively you could try:
su -l sickrage -c "/opt/sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/opt/sick"
I’m not sure that the datadir is really /opt/sick, so you’ll need to repeat in full the ExecStart command from the sickrage.service file.