-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SickRage stops after GIT update #4
Comments
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? |
I will see what I can do. |
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. |
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. |
hello... i had to reboot the nas because an unrelated problem and then the package won't start unistall install fix the issue
|
Normally the pidfile is removed when a package is stopped. 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.. |
Hey @BenjV , thanks for your comment. What shoud i Write into the sickbeard custom? Nozhing seems to work :( Thank you. |
In the Fork URL field fill in:
In the Branch field fill in:
|
Thank you a million, both of you 👍 |
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!
The text was updated successfully, but these errors were encountered: