Issue with Sickrage

[Arvi LEFEVRE]

Hello!
I've had my NAS working for a while now, everything was fine, but last Saturday I got a power outage. When the NAS restarted, everything worked, except sickrage, the jail is on, everything is mounted, but the plugin won't start.

I'm really not a BSD expert with the jail system, do you know where I can check to see what's wrong?

Thanks :)

 

[Joshua Parker Ruehlig]

what's the output of the following in the sickrage jail?

Code:

service sickrage onestart

 

[Arvi LEFEVRE]

Code:

root@sickrage_1:/ # service sickrage start                                                                                    
Starting sickrage.                                                                                                            
Traceback (most recent call last):                                                                                            
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/SickBeard.py", line 90, in <module>                                   
    import sickbeard                                                                                                          
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/__init__.py", line 37, in <module>                          
    from sickbeard import providers, metadata, config, webserveInit                                                           
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/providers/__init__.py", line 54, in <module>                
    import generic                                                                                                            
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/providers/generic.py", line 32, in <module>                 
    from sickbeard import helpers, classes, logger, db                                                                        
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/helpers.py", line 60, in <module>                           
    from sickbeard.subtitles import isValidLanguage                                                                           
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/subtitles.py", line 25, in <module>                         
    from sickbeard import helpers                                                                                             
ImportError: cannot import name helpers                                                                                       
/usr/local/etc/rc.d/sickrage: WARNING: failed to start sickrage

I had a jail with sickbeard before, but because I started to use sickrage I removed sickbeard. I don't remember if I restarted after that. I re-installed a new jail with sickbeard but I still have this problem :(

 

[Joshua Parker Ruehlig]

this is program specific, post on the sickrage forum for help.

or you could try the following to refresh your sickrage source.
* upload a second plugin to the sickrage jail
* delete sickrage
* upload the sickrage PBI to the sickrage jail
* delete the second plugin installed to the sickrage jail

PBIs available here
http://download.freenas.org/plugins/9/x64/

 

[Arvi LEFEVRE]

Hi, I'm back, I think there is a problem with the plugin, I re-installed, it worked fine for 3 days, and now it doesn't start again. I will ask on their forum, but that's really annoying, I have to re-configure everything again now... I planned to save the conf this weekend, but didn't even have time, it's crashed again...

Problerm is different this time btw, it does this:

Code:

root@sickrage_1:/ # service sickrage onestart                                                                                      
Removing stale pidfile.                                                                                                            
Starting sickrage. 

And that's all, but it's not started, when I status, it says not running.

 

[Joshua Parker Ruehlig]

Hi, I'm back, I think there is a problem with the plugin, I re-installed, it worked fine for 3 days, and now it doesn't start again. I will ask on their forum, but that's really annoying, I have to re-configure everything again now... I planned to save the conf this weekend, but didn't even have time, it's crashed again...

Problerm is different this time btw, it does this:

Code:

root@sickrage_1:/ # service sickrage onestart                                                                                      
Removing stale pidfile.                                                                                                            
Starting sickrage. 

And that's all, but it's not started, when I status, it says not running.

I doubt the plugin is broken all together as some people (including myself) run it without issue. most of the time it's a bad update on sickrage's side that causes it not to start. I think I can even spot one here
https://github.com/SiCKRAGETV/SickRage/commits/master

you can check for logs in /var/db/sickrage. also you could edit the 'command_args' in /usr/local/etc/rc.d/sickrage and remove the "-d" flag. then when you try starting sickrage any startup errors should present themselves.

 

[Krowvin]

I had the same problem @Arvi LEFEVRE, sickrage wouldn't start:

Code:

root@sickrage_1:/ # service sickrage onestart                                                                                      
Removing stale pidfile.                                                                                                            
Starting sickrage.

And going off of what @Joshua Parker Ruehlig said, it was probably an update that caused sickrage to fail. I looked in the logs a little and attempted to debug. Best I could dig up was something along the lines of special characters.

Anyways, to fix it I did the following:
1) Make a backup of the current sickrage database

Code:

cd /var/db/sickrage
cp sickbeard.db sickbeard.db.old

2) Copy one of the older database backups over to the current

Code:

cp sickbeard.db.v## sickbeard.db

3) Check and make sure the permissions are 644 or rw-r--r--

Code:

ll