[Not Solved]
Oct 05, 2016, 11:28 AM
(This post was last modified: Oct 05, 2016, 11:29 AM by lostprophet.
Edit Reason: add info
)
Hi everybody,
It seems that I might have an issue with SickRage installed on a Minibian fresh image. I am using a Pi3 as platform and Minibian. After installing and configuring all the setup, I installed Monit and configured it to monitor all the services including SickRage. Since a couple of days it is literally spamming me with emails:
Execution failed Service SickRage
Date: Wed, 05 Oct 2016 14:22:29
Action: alert
Host: RaspberryPi3
Description: failed to stop (exit status 0) -- no output
Execution succeeded Service SickRage
Date: Wed, 05 Oct 2016 14:23:31
Action: alert
Host: RaspberryPi3
Description: process is running after previous exec error (slow starting or manually recovered?)
and so on. If I try to open the webpage of SickRage it does not load and the sudo service sickrage status shows:
root@RaspberryPi3:~# sudo service sickrage status
● sickrage.service - LSB: starts instance of SickRage
Loaded: loaded (/etc/init.d/sickrage)
Active: failed (Result: exit-code) since Wed 2016-10-05 12:36:12 EEST; 1h 49min ago
Process: 18880 ExecStop=/etc/init.d/sickrage stop (code=exited, status=1/FAILURE)
Process: 462 ExecStart=/etc/init.d/sickrage start (code=exited, status=0/SUCCESS)
Oct 05 14:11:04 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:12:38 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:14:11 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:15:45 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:17:18 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:18:52 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:20:26 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:22:00 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:23:33 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:25:06 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
If I start it using the start argument, it starts - works for a while and then the spamming starts again as the service is down again and gives me this message:
root@RaspberryPi3:~# sudo service sickrage status
● sickrage.service - LSB: starts instance of SickRage
Loaded: loaded (/etc/init.d/sickrage)
Active: active (running) since Wed 2016-10-05 14:28:28 EEST; 3s ago
Process: 18880 ExecStop=/etc/init.d/sickrage stop (code=exited, status=1/FAILURE)
Process: 6250 ExecStart=/etc/init.d/sickrage start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/sickrage.service
└─6296 /usr/bin/python2.7 SickBeard.py -q --daemon --nolaunch --pidfile=/home/pi/.sickrage.pid --datadir=/opt/sickrage
Oct 05 14:28:20 RaspberryPi3 sickrage[6250]: Starting SickRage
Oct 05 14:28:28 RaspberryPi3 systemd[1]: Started LSB: starts instance of SickRage.
When it works - it searches for the shows, sends them to Transmission correctly, takes them and renames them - working as it should - until it stops all of a sudden and goes in this loop.
Does anyone have a clue of what's going on? Or how to get some logs to see what is going on?
Thank you.
It seems that I might have an issue with SickRage installed on a Minibian fresh image. I am using a Pi3 as platform and Minibian. After installing and configuring all the setup, I installed Monit and configured it to monitor all the services including SickRage. Since a couple of days it is literally spamming me with emails:
Execution failed Service SickRage
Date: Wed, 05 Oct 2016 14:22:29
Action: alert
Host: RaspberryPi3
Description: failed to stop (exit status 0) -- no output
Execution succeeded Service SickRage
Date: Wed, 05 Oct 2016 14:23:31
Action: alert
Host: RaspberryPi3
Description: process is running after previous exec error (slow starting or manually recovered?)
and so on. If I try to open the webpage of SickRage it does not load and the sudo service sickrage status shows:
root@RaspberryPi3:~# sudo service sickrage status
● sickrage.service - LSB: starts instance of SickRage
Loaded: loaded (/etc/init.d/sickrage)
Active: failed (Result: exit-code) since Wed 2016-10-05 12:36:12 EEST; 1h 49min ago
Process: 18880 ExecStop=/etc/init.d/sickrage stop (code=exited, status=1/FAILURE)
Process: 462 ExecStart=/etc/init.d/sickrage start (code=exited, status=0/SUCCESS)
Oct 05 14:11:04 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:12:38 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:14:11 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:15:45 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:17:18 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:18:52 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:20:26 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:22:00 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:23:33 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
Oct 05 14:25:06 RaspberryPi3 systemd[1]: Stopped LSB: starts instance of SickRage.
If I start it using the start argument, it starts - works for a while and then the spamming starts again as the service is down again and gives me this message:
root@RaspberryPi3:~# sudo service sickrage status
● sickrage.service - LSB: starts instance of SickRage
Loaded: loaded (/etc/init.d/sickrage)
Active: active (running) since Wed 2016-10-05 14:28:28 EEST; 3s ago
Process: 18880 ExecStop=/etc/init.d/sickrage stop (code=exited, status=1/FAILURE)
Process: 6250 ExecStart=/etc/init.d/sickrage start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/sickrage.service
└─6296 /usr/bin/python2.7 SickBeard.py -q --daemon --nolaunch --pidfile=/home/pi/.sickrage.pid --datadir=/opt/sickrage
Oct 05 14:28:20 RaspberryPi3 sickrage[6250]: Starting SickRage
Oct 05 14:28:28 RaspberryPi3 systemd[1]: Started LSB: starts instance of SickRage.
When it works - it searches for the shows, sends them to Transmission correctly, takes them and renames them - working as it should - until it stops all of a sudden and goes in this loop.
Does anyone have a clue of what's going on? Or how to get some logs to see what is going on?
Thank you.