SYNO-packages icon indicating copy to clipboard operation
SYNO-packages copied to clipboard

SickRage stops after GIT update

Open DavidJares opened this issue 6 years ago • 10 comments

Hello @BenjV ,

first of all, thanks a million for this fix. It really helped me a lot, however, I noticed from time to time that this package stopped working for no reason. Everything was clear after last GIT update. Once I update my GIT, this package stops and it is impossible to start it again. Only thing I can do is uninstall and install again. May I kindly ask you for your help?

Thank you!

DavidJares avatar Jan 29 '18 20:01 DavidJares

I am also suffering from this at the moment, have to grab the backup files manually and then uninstall reinstall then copy files back over if the server is rebooted (or a power out which has happened a few times in the last week) Any logs we can send you to assist?

arejaytee avatar Feb 12 '18 05:02 arejaytee

I will see what I can do. I myself don't have any problems at all and I also update git.

BenjV avatar Feb 13 '18 16:02 BenjV

For reference I don't know whether it was git or upgrading to 6.1.5-15254 the two were done very close together, but it was not until I the server rebooted that sickrage wouldn't restart.

arejaytee avatar Feb 14 '18 05:02 arejaytee

Had the same issue (or so I thought). I noticed it after a reboot: Sickrage didn't start automatically, and I couldn't start it from the Synology web interface. I played with synopkgctl a bit and finally found the cause of the problem for me: the PID file wasn't deleted after the reboot... Which prevented Sickrage from restarting. Deleted it by hand, and boom it works...

Schnouki avatar May 02 '18 15:05 Schnouki

hello... i had to reboot the nas because an unrelated problem and then the package won't start unistall install fix the issue but latter I found somewhere in the logs:

2018/08/09 13:10:02     start sickrage 99999999 Begin start-stop-status start
PID file: /var/packages/sickrage/target/var/sickrage.pid already exists. Exiting.

crlshn avatar Aug 09 '18 21:08 crlshn

Normally the pidfile is removed when a package is stopped. When you do something like a hard reboot or lose power the pidfile is not removed. It is a little flaw in the package script. Solution is to delete the pidfile yourself.

If it bother you uninstall the package and then use sickbeard-custom from the SynoCommunity and replace the sickbeard with sickrage when ask for the fork.. The SynoCommunity packages are now supporting DSM 6

BenjV avatar Aug 10 '18 11:08 BenjV

Hey @BenjV , thanks for your comment. What shoud i Write into the sickbeard custom? Nozhing seems to work :( Thank you.

DavidJares avatar Aug 14 '18 19:08 DavidJares

for sickbeard-custom you may follow this or this ... unless you are like me and destroy /volume1 and get stuck unable to install sickbeard-custom...

crlshn avatar Aug 14 '18 20:08 crlshn

In the Fork URL field fill in:

git://github.com/SickRage/SickRage.git

In the Branch field fill in:

master

BenjV avatar Aug 15 '18 07:08 BenjV

Thank you a million, both of you 👍

DavidJares avatar Aug 16 '18 17:08 DavidJares