New sickrage repo?

[John Zoch]

I solved my SickRage "add new shows" problem. IPv6 was turned on in my jail. I have IPv6 turned off on my PFSense router and the Jails seem pretty insistent upon using IPv6. I had to select the jail, select settings and clear out several IPv6 fields to get it to finally take. Unchecking just the IPv6 checkbox wasn't enough. I'd go back into settings and the IPv6 checkbox would be turned on again.

A clue that you might have this problem is the jail DNS doesn't work. If you can ping 8.8.8.8 but you can't ping google.com check /etc/resolv.conf. You might find there's no hostname entries there. When I turned IPv6 off and restarted the jail, the /etc/resolv.conf file showed hostname 192.168.0.1.

I will probably turn PFSense IPv6 back on because it didn't solve a problem I had with another device.

Thanks to everyone who threw ideas at me.

John

 

[fontes31]

in /var/db/sickrage

thank you Joshua, worked perfect.

 

[Prasanth]

The answer is in this thread... it's not that long.

But to save you time, find the config.ini file and remove the line with the current commit hash ID. Then restart the plugin and try to update (in sickrage webUI, may take 2-3x, but eventually figures itself out)

Tried this method and no luck. I get a the following warning:

2015-12-22 22:30:32 MAIN :: git symbolic-ref -q HEAD returned : fatal: Not a git repository (or any of the parent directories): .git
2015-12-22 22:30:32 CHECKVERSION :: git symbolic-ref -q HEAD returned : fatal: Not a git repository (or any of the parent directories): .git
2015-12-22 22:30:32 CHECKVERSION :: git rev-parse HEAD returned : fatal: Not a git repository (or any of the parent directories): .git
​

Any other way to get the auto update to work.

 

[Joshua Parker Ruehlig]

Tried this method and no luck. I get a the following warning:

2015-12-22 22:30:32 MAIN :: git symbolic-ref -q HEAD returned : fatal: Not a git repository (or any of the parent directories): .git
2015-12-22 22:30:32 CHECKVERSION :: git symbolic-ref -q HEAD returned : fatal: Not a git repository (or any of the parent directories): .git
2015-12-22 22:30:32 CHECKVERSION :: git rev-parse HEAD returned : fatal: Not a git repository (or any of the parent directories): .git
​

Any other way to get the auto update to work.

This plugin doesn't use git by default. Not sure why sickrage is even bringing up git as my log has this instead

Code:

CHECKVERSION :: Checking for updates using SOURCE

What steps did you do this far after upgrading?

 

[Prasanth]

This plugin doesn't use git by default. Not sure why sickrage is even bringing up git as my log has this instead

Code:

CHECKVERSION :: Checking for updates using SOURCE

What steps did you do this far after upgrading?

So initially I had upgraded manually using the CLI on my server using the steps outlined at the beginning of this thread, but then I saw your post that I could just upgrade right from the freenas GUI so I went ahead and updated that(I always worry whether those updates within GUI are safe or will break any of the customization your install instructions gave). I started getting the error listed above. I then tried the deleting of the line in the config.ini file and had no luck even after restarting multiple times. That's when I posted above. Since then I actually deleted my plugin and reinstalled from your download link on your site. I actually didn't have to even restore from the back up. The configuration all stayed in place.

Thanks!

 

[Joshua Parker Ruehlig]

So initially I had upgraded manually using the CLI on my server using the steps outlined at the beginning of this thread, but then I saw your post that I could just upgrade right from the freenas GUI so I went ahead and updated that(I always worry whether those updates within GUI are safe or will break any of the customization your install instructions gave). I started getting the error listed above. I then tried the deleting of the line in the config.ini file and had no luck even after restarting multiple times. That's when I posted above. Since then I actually deleted my plugin and reinstalled from your download link on your site. I actually didn't have to even restore from the back up. The configuration all stayed in place.

Thanks!

great, glad it's working.

so maybe the .git folder from the manual repo change was still there.

 

[one800higgins]

Just to chime in and repeat what everyone else is saying.

After reading this thread, I originally updated via the Update button in the FreeNAS UI. Started getting the Github issues, so I wiped the `last_commit_hash` from `config.ini`, as SickRage's Github issues suggested. After restarting, SR was saying to update since it didn't have a hash ID, but it simply wouldn't update. It would just kick off a back-up and then not proceed.

So, I stopped the service and followed the steps that @overthinkingme posted, replacing the source completely with the latest build and now it's running without a hitch.

 

[rawkus]

updated using the update button in freenas and now i am getting an error when trying to access sickrage's gui. My web browser is giving me the error " The page isn't redirecting properly" any idea what could be causing this?

was able to fix my issue by deleting the plugin and reinstalling

 

[hertzsae]

Thanks to everyone that helped here!

My sickrage has been failing to post process since December 19th. It's also failed to stay running for more than a day for probably just as long (but I don't have the logs to prove it). Using various directions here, I was able to get everything working again. Due to the fact that I had to piece together a few posts, I figured I'd put everything that worked for me in a single post.

1) Stopped the plugin in the freenas GUI on the "Plugins - Installed" tab by setting the service status to off. Due to problems with sickrage, this didn't actually stop it, but ensured the plugin is stopped after a reboot.
2) Rebooted freenas. When freenas came up, the plugin was in a stopped state.
3) Backed up /var/db/sickrage/config.ini, sickbeard.db, and failed.db to my backup folder in my media directory
4) Deleted /var/db/sickrage/cache.db
5) Removed the entire line starting with "cur_commit_hash =" from /var/db/sickrage/config.ini (the line will reappear later)
6) Updated the plugin in the freenas GUI.
7) After it updated, I started the plugin.
8) The sickrage GUI said that it didn't know what version it was on and had a link to update that I clicked. I compared the hash of the install to github and I'm current.

Everything now works and best of all my nzbtomedia scripts are running without issue.

Note that I was coming from sickrageTV with commit hash 9226ba5 from Dec 22nd.
My nzbtomedia is on commit hash 3e4861e from Dec 11th.

 

[Supa]

Is anyone getting constant warning errors in SickRage or just me?

2016-01-11 18:17:33 MAIN :: Connection error to getURL http://thexem.de/map/allNames?origin=tvdb&seasonNumbers=1 Error: u"error HTTPConnectionPool(host='thexem.de', port=80): Max retries exceeded with url: /map/allNames?origin=tvdb&seasonNumbers=1 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 60] Operation timed out',))" [7fd6c98]

I used some google foo.. saw it might had to do with upgrading python / SSL. but not sure. I just deleted the cache.db and restarted so I guess I'll wait and see.

 

[Joshua Parker Ruehlig]

Is anyone getting constant warning errors in SickRage or just me?

2016-01-11 18:17:33 MAIN :: Connection error to getURL http://thexem.de/map/allNames?origin=tvdb&seasonNumbers=1 Error: u"error HTTPConnectionPool(host='thexem.de', port=80): Max retries exceeded with url: /map/allNames?origin=tvdb&seasonNumbers=1 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 60] Operation timed out',))" [7fd6c98]

I used some google foo.. saw it might had to do with upgrading python / SSL. but not sure. I just deleted the cache.db and restarted so I guess I'll wait and see.

That error probably has nothing to do with SSL. It's connecting to the server without SSL.

 

[Grantp]

I know this is an old thread but it seems the right place to ask my question. This appeared on the news page within SickRage

2017-07-20
A false DMCA takedown request was sent to GitHub, resulting in multiple repositories, including SickRage/SickRage, to be taken down. We're countering this and should have the repo back very soon. We thank you for your patience.

Since then I haven't received any update to SickRage.

A few days later this was placed on the news page,

2017-08-05
Our main repository on Github SickRage/SickRage is now available.
If you installed SickRage using a mirror of our repository, or switched your installation to get updates from a mirror, please make sure that you're back on the main repo URL in order to be able to receive future updates.
The basic set of commands is described here: git remote set-url origin https://github.com/SickRage/SickRage.git git fetch origin git checkout master git branch -u origin/master git reset --hard origin/master git pull

This is a link to a page on the SickRage Forum https://www.sickrage.ca/forums/foru...te-or-switch-to-sickrage-if-already-installed

My question is how do I get SickRage to start updating again if I try the above instructions I get the following

root@sabnzbd_1:/usr/pbi/sickrage-amd64/share/sickrage/SickRage # git remote rm origin
fatal: Not a git repository (or any of the parent directories): .git

Any help would be appreciated

Thanks Grant

 

[Moppen]

Hi Grant (and everybody else),

any News on this Topic? I have the same problem here ...
Since yesterday even the "Unknown current version number: If you've never used the SickRage upgrade system before then current version is not set. — Update Now"-Errormessage pops up again. Of course, if I hit "Update now", I get a "Update failed" Message.

I was told in another thread not to temper with git in the jail and the best thing would be to wait for an update. But still there is no update of the plugin, yet.

Any help would be appreciated, too.

Regards,
Stefan

 

[Moppen]

Interesting. This Morning the well-known Update-Message showed up und told me that I am 106 commits behind. I tried to update but a horrible error-message occured. After heading back to the Sickrage-page the update-message was gone (again).

 

[Moppen]

and again the update-message popped up and this time the update seemed to have run through. Changelog says now: "v2017.12.16-1"

 

[Maturola]

Interesting. This Morning the well-known Update-Message showed up und told me that I am 106 commits behind. I tried to update but a horrible error-message occured. After heading back to the Sickrage-page the update-message was gone (again).

I fixed the whole no starting after update mess yesterday, moving to the Sickchill repo, and I am now getting this error as well, updating from UI does nothing, but logs show no errors

Code:

Unknown current version number: If you've never used the SickRage upgrade system before then current version is not set.— Update Now

Code:

2018-11-15 10:30:45 INFO	 CHECKVERSION :: Checking for updates using SOURCE
2018-11-15 10:30:45 INFO	 TORNADO :: Starting SickRage on http://0.0.0.0:8081/
2018-11-15 10:30:45 INFO	 MAIN :: 301567: Unable to find IMDb show info in the database
2018-11-15 10:30:45 INFO	 MAIN :: Writing PID: 55156 to /var/run/sickrage/sickrage.pid
2018-11-15 10:30:41 INFO	 EVENT-QUEUE :: Restarting SickRage with ['/usr/pbi/sickrage-amd64/bin/python2.7', '/usr/pbi/sickrage-amd64/share/sickrage/SickRage/SickBeard.py', '--datadir', '/var/db/sickrage', '-d', '--pidfile', '/var/run/sickrage/sickrage.pid', '-q', '--nolaunch']
2018-11-15 10:30:41 INFO	 EVENT-QUEUE :: Shutting down Tornado
2018-11-15 10:30:41 INFO	 EVENT-QUEUE :: Saving config file to disk
2018-11-15 10:30:38 INFO	 EVENT-QUEUE :: Saving all shows to the database
2018-11-15 10:30:37 INFO	 EVENT-QUEUE :: Waiting for the SUBTITLESFINDER thread to exit
2018-11-15 10:30:37 INFO	 EVENT-QUEUE :: Waiting for the PROPERFINDER thread to exit
2018-11-15 10:30:36 INFO	 EVENT-QUEUE :: Waiting for the TRAKTCHECKER thread to exit
2018-11-15 10:30:35 INFO	 EVENT-QUEUE :: Waiting for the POSTPROCESSER thread to exit
2018-11-15 10:30:35 INFO	 EVENT-QUEUE :: Waiting for the SEARCHQUEUE thread to exit
2018-11-15 10:30:35 INFO	 EVENT-QUEUE :: Waiting for the SHOWQUEUE thread to exit
2018-11-15 10:30:34 INFO	 EVENT-QUEUE :: Waiting for the VERSIONCHECKER thread to exit
2018-11-15 10:30:34 INFO	 EVENT-QUEUE :: Waiting for the SHOWUPDATER thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Waiting for the BACKLOG thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Waiting for the DAILYSEARCH thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Waiting for the EVENTS thread to exit
2018-11-15 10:30:33 INFO	 EVENT-QUEUE :: Aborting all threads
2018-11-15 10:30:32 INFO	 Thread-62 :: Moving files from /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update/SiCKRAGE-SiCKRAGE-dd00ab8 to /usr/pbi/sickrage-amd64/share/sickrage/SickRage
2018-11-15 10:30:32 INFO	 Thread-62 :: Deleting file /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update/sr-update.tar
2018-11-15 10:30:32 INFO	 Thread-62 :: Extracting file /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update/sr-update.tar
2018-11-15 10:30:30 INFO	 Thread-62 :: Downloading update from 'http://github.com/SickRage/SickRage/tarball/master'
2018-11-15 10:30:30 INFO	 Thread-62 :: Creating update folder /usr/pbi/sickrage-amd64/share/sickrage/SickRage/sr-update before extracting
2018-11-15 10:30:30 INFO	 Thread-62 :: Config backup successful, updating...
2018-11-15 10:30:20 INFO	 Thread-62 :: Config backup in progress...