Sickchill: Sickrage wont start after last update

Created on 11 Apr 2016  Â·  10Comments  Â·  Source: SickChill/SickChill

Before submitting your issue:

Enable debug logging in SickRage settings, reproduce the error (be sure to disable after the bug is fixed)

Branch/Commit:SickRage Updated : SickRage Updated To Commit#: 394072f7cd865dcd0472e503fb903206b36d25f7
OS:synolgy
What you did: auto update
What happend: sickrage wont start up
What you expected:
Logs:

PASTE LOGS HERE
Bug / Issue Fixed

Most helpful comment

I've also experienced this today and the good old git pull fixed it for me. More complete instructions below:

1 - ssh into your synology, e.g. using putty or terminal (ssh root@<synology IP> and use your admin password when prompted);
2 - Then:

cd /volume1/@appstore/sickbeard-custom/var/SickBeard
/volume1/@appstore/git/bin/git pull

3 - start SickRage from Synology's GUI.

All 10 comments

Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked

  • [ ] Include basic information: Branch/Commit, OS, What you did, What happened, What you expected
  • [ ] Enable debug logging (be sure to disable after the bug is fixed)
  • [ ] Post debug logs, either inline (for smaller logs) or using gist

Please make sure you also read how to create an issue and followed all of the steps.

The title should describe your issue. Having "SR not working" or "I get this bug" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.

Sometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.

Thanks!

same here

The very last commit, from just a few minutes ago, seems to have resolved it for me. Try to pull the latest verison now.

How? Auto update does not work now. Sickrage is down on my synology.

Verzonden vanuit Outlook Mobile

On Mon, Apr 11, 2016 at 12:21 PM -0700, "AnatomicFlack" [email protected] wrote:

The very last commit seems to have resolved it for me. Try to pull the latest verison now.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

The last commit will fix this. Use this on your Synology (Terminal):

git reset --hard HEAD
git clean -f
git pull

Ok. I am a user, not programmer. Do I use putty to make connection to sygnolgy? And then?

Verzonden vanuit Outlook Mobile

On Mon, Apr 11, 2016 at 12:24 PM -0700, "Ricardo Jacobs" [email protected] wrote:

The last commit will fix this. Use this on your Synology (Terminal):

git reset --hard HEAD
git clean -f
git pull

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

I've also experienced this today and the good old git pull fixed it for me. More complete instructions below:

1 - ssh into your synology, e.g. using putty or terminal (ssh root@<synology IP> and use your admin password when prompted);
2 - Then:

cd /volume1/@appstore/sickbeard-custom/var/SickBeard
/volume1/@appstore/git/bin/git pull

3 - start SickRage from Synology's GUI.

@dmarcelino Works like a charm thx

This was very strange, it only broke on the syno. Anyways, fixed it now.

It broke inside my FreeNAS jail as well, but it's fixed with the current state of master :wink:.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Raymoz101 picture Raymoz101  Â·  4Comments

mofman picture mofman  Â·  4Comments

CaptainConsternant picture CaptainConsternant  Â·  4Comments

Hydrog3n picture Hydrog3n  Â·  4Comments

dilruwan7 picture dilruwan7  Â·  3Comments