Sickrage app

evylrat
Posts: 103
Joined: Sun Jan 02, 2011 6:37 pm

Sickrage app

Postby evylrat » Wed Oct 17, 2018 8:12 am

I know I'm not the only one who's found their sickrage app has imploded and become unusable in the last week and I was hoping a solution may have been posted on the amahi forums.
The issue appears to be in the form of recent commits that stop the app from functioning correctly.
With my database loaded (or any known working backup) I get the 503 error. If I start fresh and let sickrage update, I can generate a few thousand warning messages an hour about network timezones not being found.
It seems the solution is to switch repo to another fork, however my Linux knowledge is too limited to execute this task.
I understand I have to change the git fork in the config.ini AND go to the actual git folder (can't find it) and run the git remote set origin command, but that's where I'm stuck.
This initially was on Amahi 9, but I'll be on 11 by the end of the week if that's an issue.

User avatar
bigfoot65
Project Manager
Posts: 11063
Joined: Mon May 25, 2009 4:31 pm

Re: Sickrage app

Postby bigfoot65 » Wed Oct 17, 2018 10:04 am

I understand I have to change the git fork in the config.ini AND go to the actual git folder (can't find it) and run the git remote set origin command, but that's where I'm stuck.
The Amahi app is not configured in that way. A new app would need to be built based on the new version.

I see it came in as an app suggestion. It will be added to the list, but please understand it may not be ready for use as quick as you might desire.

Maybe someone in the community can help you with manual guidance.
ßîgƒσστ65
Applications Manager

madhatta
Posts: 22
Joined: Tue Oct 09, 2018 8:56 pm

Re: Sickrage app

Postby madhatta » Thu Oct 18, 2018 1:10 am

This may not be useful, but after experiencing the same problems with Sickrage, I have switched over to Sonarr and couldn't be happier. I still check the commits every few days and update the sickrage app when I see one, out of pure interest, but that problem doesn't seem to be going away :-/.

evylrat
Posts: 103
Joined: Sun Jan 02, 2011 6:37 pm

Re: Sickrage app

Postby evylrat » Thu Oct 18, 2018 11:33 am

Thanks, I'll take a look at Sonarr. I never got round to using usenet, I purely used sickrage to move and rename files, I presume Sonarr has the same functionality to allow you to download files yourself.

madhatta
Posts: 22
Joined: Tue Oct 09, 2018 8:56 pm

Re: Sickrage app

Postby madhatta » Thu Oct 18, 2018 10:10 pm

Thanks, I'll take a look at Sonarr. I never got round to using usenet, I purely used sickrage to move and rename files, I presume Sonarr has the same functionality to allow you to download files yourself.
Yes but I am not sure if there is a way to manually invoke a move/rename. Everything is done with API calls, as near as I can tell. So it searches your index (or tracker if using with torrents) and then sends the nzb/torrent to the watched folder for your downloader. It then keeps track of where the completed files are moved to through the API calls and moves/renames accordingly. The only thing I have found close to manual post processing is if it has a job that has not finished you can go into activity and tell it where the file is.

If you dump all the files into the proper folder though it will index them appropriately and then you can run a mass rename. on the Folder. Again, they have to be in the proper folder already, as near as I can tell.

evylrat
Posts: 103
Joined: Sun Jan 02, 2011 6:37 pm

Re: Sickrage app

Postby evylrat » Sat Oct 20, 2018 2:28 am

Great, thank you!

For others who might know how to fix it "the dirty way" take a look at https://github.com/SickChill/SickChill/ ... n-packages, and please post any success stories, else I fear this is the end for the sickrage app.

If you check out the site and reddit groups you can read how a former member of the team was able to change the code and boot other members, it's all a bit political; makes for an interesting read. Redirects were changed, which is why the log is full of network_timezone errors.
Original members have created a new fork, the one I would like to get working.
As this app isn't mission critical I don't expect a fix, as madhatta says it might be time to move on

Who is online

Users browsing this forum: No registered users and 2 guests