Skip to content
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

Open
DavidJares opened this issue Jan 29, 2018 · 10 comments
Open

SickRage stops after GIT update #4

DavidJares opened this issue Jan 29, 2018 · 10 comments

Comments

@DavidJares
Copy link

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!

@arejaytee
Copy link

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?

@BenjV
Copy link
Owner

BenjV commented Feb 13, 2018

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

@arejaytee
Copy link

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.

@Schnouki
Copy link

Schnouki commented May 2, 2018

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...

@crlshn
Copy link

crlshn commented Aug 9, 2018

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.

@BenjV
Copy link
Owner

BenjV commented Aug 10, 2018

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

@DavidJares
Copy link
Author

DavidJares commented Aug 14, 2018

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

@crlshn
Copy link

crlshn commented Aug 14, 2018

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...

@BenjV
Copy link
Owner

BenjV commented Aug 15, 2018

In the Fork URL field fill in:

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

In the Branch field fill in:

master

@DavidJares
Copy link
Author

Thank you a million, both of you 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants