[SOLVED] Sickrage doesn't start since the last update of OSMC

Help and Support
1

Hey everyone,
today I watched Sickrage and everything was OK. After that OSMC downloaded an update.
I don’t know if the update is the cause, but now sickrage doesn’t start.

Someone can help me ?
When I type :
sudo service sickrage start

the result is :
Job for sickrage.service failed. See 'systemctl status sickrage.service' and 'journalctl -xn' for details.

So i looked the status :
systemctl status sickrage.service

the result is :
sickrage.service - SickRage Daemon Loaded: loaded (/etc/systemd/system/sickrage.service; enabled) Active: failed (Result: exit-code) since mar. 2016-05-03 19:18:25 CEST; 26s ago Process: 2965 ExecStart=/opt/sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/opt/sickrage (code=exited, status=1/FAILURE)

And the journal :
sudo journalctl -xn

`-- Logs begin at mar. 2016-05-03 16:18:51 CEST, end at mar. 2016-05-03 19:28:48 CEST. –
mai 03 19:18:25 osmc SickBeard.py[2965]: configobj.ParseError: Invalid line at line “859”.
mai 03 19:18:25 osmc systemd[1]: sickrage.service: control process exited, code=exited status=1
mai 03 19:18:25 osmc systemd[1]: Failed to start SickRage Daemon.
– Subject: L’unité (unit) sickrage.service a échoué
– Defined-By: systemd
– Support: systemd-devel Info Page

– L’unité (unit) sickrage.service a échoué, avec le résultat failed.
mai 03 19:18:25 osmc systemd[1]: Unit sickrage.service entered failed state.
mai 03 19:18:25 osmc sudo[2947]: pam_unix(sudo:session): session closed for user root
mai 03 19:18:56 osmc sudo[2984]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/systemctl
mai 03 19:18:56 osmc sudo[2984]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
mai 03 19:18:56 osmc sudo[2984]: pam_unix(sudo:session): session closed for user root
mai 03 19:28:48 osmc sudo[3090]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/journalctl
mai 03 19:28:48 osmc sudo[3090]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)`

Thanks for your help.
Greg

2

Your configuration file is not valid or possibly malformed

Delete the config file or check line 859

I don’t believe this is an OSMC issue as we don’t distribute this via our App Store

3

Hello thanks for your answer.

I fixed it (i don’t know if it’s the good way, but I think it work :wink:)

I edited the config file and delete the line 859. I restarted sickrage and it seems to works…

For others users that have the same problem :

edit the config.ini file

sudo nano /opt/sickrage/config.ini
(or copy it to your local drive to edit with a “real” text editor)

delete the line 859 (for me, it was the last line)
search and delete : log_nr

then be sure the file is writable :
cd /opt/sickrage
ls -l

be sure to have this line :
-rw-rw-rw- 1 root root 20472 mai 4 11:11 config.ini

if you don’t have this line :
sudo chmod a+w /opt/sickrage/config.ini

then restart sickrage :
sudo service sickrage start

thank you @sam_nazarko, even you don’t really answer you put me on the right way :slight_smile:

Thanks again for this awesome OSMC !!!

Greg

4

Guy, I’m getting the same error after updating OSMC. Sickrage was working nicely before.
I tried @Gregory_B tutorial but my log doesn’t show an invalid line such the “859”. Deleting “log_nr” didn’t work.

Bellow is the journal log. Any ideas?

– Logs begin at Sat 2018-11-24 16:51:26 -02, end at Sun 2018-11-25 12:06:48 -02. –

nov 25 12:04:07 osmc sudo[10164]: osmc : TTY=pts/0 ; PWD=/opt/sickrage ; USER=root ; COMMAND=/usr/sbin/service sickrage star

nov 25 12:04:07 osmc sudo[10164]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)

nov 25 12:04:08 osmc systemd[1]: Starting SickRage Daemon…

– Subject: Unidade sickrage.service sendo iniciado

– Defined-By: systemd

– Support: Debian -- User Support

–

– A unidade sickrage.service está sendo iniciada.

nov 25 12:05:38 osmc systemd[1]: sickrage.service: Start operation timed out. Terminating.

nov 25 12:05:39 osmc systemd[1]: Failed to start SickRage Daemon.

– Subject: A unidade sickrage.service falhou

– Defined-By: systemd

– Support: Debian -- User Support

–

– A unidade sickrage.service falhou.

–

– O resultado é failed.

nov 25 12:05:39 osmc systemd[1]: sickrage.service: Unit entered failed state.

nov 25 12:05:39 osmc systemd[1]: sickrage.service: Failed with result ‘timeout’.

nov 25 12:05:39 osmc sudo[10164]: pam_unix(sudo:session): session closed for user root

nov 25 12:06:48 osmc sudo[10222]: osmc : TTY=pts/0 ; PWD=/opt/sickrage ; USER=root ; COMMAND=/bin/journalctl -xn

nov 25 12:06:48 osmc sudo[10222]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)

5

@sam_nazarko can you give a hand on this issue?

6

Instead of re-opening a post from 3 years ago, that probably is not related to your problem, you should instead start a new thread. And as always, a support request should include logs! Without logs you are not going to get much help.

7

I don’t use SickRage.

But @bmillham is right. OP’s post probably isn’t relevant to yours.
Start a new post and we’ll try and help