SickRage suddenly not starting

Status
Not open for further replies.

OlleDenStore

Cadet
Joined
Jan 30, 2015
Messages
5
Hi!
Let me start by saying I am completely new to freeNAS. So you are talking to a complete noob here :) I did however manage to install and configure it successfully. I've been running the SickRage plugin for about 3 month without any problems. Now suddenly it doesn't start. The thing that triggered it was that I installed the latest freeNAS updates yesterday. Since then the plugin just won't start. When I try to start it from plugins->installed in the gui by clicking the red off icon. I get the blue bars indicating activity for about 3 sec before it stops. The weird thing is that I don't get any error messages in the terminal. It just doesn't start.
When I start the the sickRage jail I get the following lines in the terminal:
Code:
Aug 28 00:43:22 freenas notifier: Performing sanity check on nginx configuration:
Aug 28 00:43:22 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Aug 28 00:43:22 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Aug 28 00:43:23 freenas epair1a: Ethernet address: 02:1b:3e:00:0a:0a
Aug 28 00:43:23 freenas epair1b: Ethernet address: 02:1b:3e:00:0b:0b
Aug 28 00:43:23 freenas kernel: epair1a: link state changed to UP
Aug 28 00:43:23 freenas kernel: epair1a: link state changed to UP
Aug 28 00:43:23 freenas kernel: epair1b: link state changed to UP
Aug 28 00:43:23 freenas kernel: epair1b: link state changed to UP
Aug 28 00:43:23 freenas kernel: epair1a: promiscuous mode enabled
Aug 28 00:43:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Aug 28 00:43:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Aug 28 00:43:53 freenas kernel: ifa_del_loopback_route: deletion failed
Aug 28 00:43:53 freenas Freed UMA keg (udp_inpcb) was not empty (80 items).  Lost 8 pages of memory.
Aug 28 00:43:53 freenas Freed UMA keg (udpcb) was not empty (1008 items).  Lost 6 pages of memory.
Aug 28 00:43:53 freenas Freed UMA keg (tcptw) was not empty (150 items).  Lost 3 pages of memory.
Aug 28 00:43:53 freenas Freed UMA keg (tcp_inpcb) was not empty (50 items).  Lost 5 pages of memory.
Aug 28 00:43:53 freenas Freed UMA keg (tcpcb) was not empty (20 items).  Lost 5 pages of memory.
Aug 28 00:43:53 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Aug 28 00:43:53 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required

There seems to be an awful lot of errors here.
Any and all help would be greatly appreciated!
/Olle
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
not sure why you call those errors, some are just messages put in the log.

what happens why you try starting SickRage from the commandline in the sickrage jail.
'service sickrage onestart'
 

OlleDenStore

Cadet
Joined
Jan 30, 2015
Messages
5
First off, thanks for the fast reply! I tried to launch it from the commandline like you suggested and got the following:
Code:
root@sickrage_1:/ # service sickrage onestart                                  
Starting sickrage.                                                             
su: pam_start: system error                                                    
/usr/local/etc/rc.d/sickrage: WARNING: failed to start sickrage 
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I'm guessing the permissions of your jail dataset(s) were changed.
did you ever recursively change permissions or ownership of this dataset? that will break your jail, and you'll need to install the plugin again.
you can backup and restore /var/db/sickrage to avoid having to set it up again.
 
Status
Not open for further replies.
Top