New sickrage repo?

[sp3cialk]

I originally updated via freenas plugin page. Got the error. Backed up uninstalled plugin and reinstalled fresh, as soon as I restore I start getting the error again. What in the files messes it up.

 

[Ray Milyard]

did you update the plugin or do the steps people are posting? can you guys also confirm you can ping github.com?

I updated the plugin from within FreeNAS yesterday. Today I am getting this same error.

 

[Joshua Parker Ruehlig]

can you guys ping github.com? the dev just fixed the source updater and I tested it as working, but maybe something broke since then.

 

[Ray Milyard]

can you guys ping github.com? the dev just fixed the source updater and I tested it as working, but maybe something broke since then.

I can ping it.

 

[Joshua Parker Ruehlig]

I can ping it.

can I see a screenshot of the SR home page/check for updates page. also can someone test a second fresh install of the plugin to see if it updates to the latest version.

 

[sp3cialk]

I can ping as well. If I do a fresh install I get no errors. Once I restore my config.ini/failed.db/sickbeard.db and restart I get the error

 

[Ray Milyard]

can I see a screenshot of the SR home page/check for updates page. also can someone test a second fresh install of the plugin to see if it updates to the latest version.

Not sure what looking for but here in the info I have:

Configuration
SR Version: BRANCH: (master) / COMMIT: (92b6eb03ee75db853e3fecb3367ce12d56a09abe)
SR User: media
SR Locale: ('en_US', 'UTF-8')
SR Config: /var/db/sickrage/config.ini
SR Database: /var/db/sickrage/sickbeard.db
SR Cache Dir: /var/db/sickrage/cache
SR Log Dir: /var/db/sickrage/Logs
SR Arguments: ['--datadir', '/var/db/sickrage', '-d', '--pidfile', '/var/run/sickrage/sickrage.pid', '-q', '--nolaunch']
SR Web Root: /sickrage
Python Version: 2.7.9 (default, Sep 9 2015, 14:50:03) [GCC 4.2.1 20070831 patched [FreeBSD]]
Website http://sickrage.github.io/
WiKi https://github.com/SickRage/sickrage-issues/wiki
Source https://github.com/SickRage/SickRage/
IRChat #sickrage-issues on irc.freenode.net


WARNING logs
2015-12-07 12:12:37 Thread-25 :: Unable to contact github, can't check for update: UnknownObjectException()
2015-12-07 12:09:46 CHECKVERSION :: Unable to contact github, can't check for update: UnknownObjectException()

 

[Joshua Parker Ruehlig]

I can ping as well. If I do a fresh install I get no errors. Once I restore my config.ini/failed.db/sickbeard.db and restart I get the error

thanks for the info.

I was able to get past it somehow without having to start fresh. I do remember clicking around a bit, like having to try it multiple times, and maybe even start/stop SR from the plugins>installed tab. I don't remember that github arror though.
our next step would be to see what that logs are saying, maybe we can figure out if it's an issue with the plugin or SR

 

[Joshua Parker Ruehlig]

Not sure what looking for but here in the info I have:

Configuration
SR Version: BRANCH: (master) / COMMIT: (92b6eb03ee75db853e3fecb3367ce12d56a09abe)
SR User: media
SR Locale: ('en_US', 'UTF-8')
SR Config: /var/db/sickrage/config.ini
SR Database: /var/db/sickrage/sickbeard.db
SR Cache Dir: /var/db/sickrage/cache
SR Log Dir: /var/db/sickrage/Logs
SR Arguments: ['--datadir', '/var/db/sickrage', '-d', '--pidfile', '/var/run/sickrage/sickrage.pid', '-q', '--nolaunch']
SR Web Root: /sickrage
Python Version: 2.7.9 (default, Sep 9 2015, 14:50:03) [GCC 4.2.1 20070831 patched [FreeBSD]]
Website http://sickrage.github.io/
WiKi https://github.com/SickRage/sickrage-issues/wiki
Source https://github.com/SickRage/SickRage/
IRChat #sickrage-issues on irc.freenode.net


WARNING logs
2015-12-07 12:12:37 Thread-25 :: Unable to contact github, can't check for update: UnknownObjectException()
2015-12-07 12:09:46 CHECKVERSION :: Unable to contact github, can't check for update: UnknownObjectException()

maybe it's because you're restoring your database. that commit number is from the old repo and would confuse stuff.

I didn't restore, when I ran the plugin update SR got confused and asked to update (where it grabs the latest commit and stores this value).

 

[Ray Milyard]

thanks for the info.

I was able to get past it somehow without having to start fresh. I do remember clicking around a bit, like having to try it multiple times, and maybe even start/stop SR from the plugins>installed tab. I don't remember that github arror though.
our next step would be to see what that logs are saying, maybe we can figure out if it's an issue with the plugin or SR

Well each time I check for update just get new error message. I have start/stop the plugin about 10 times now with no luck.

 

[Joshua Parker Ruehlig]

Well each time I check for update just get new error message. I have start/stop the plugin about 10 times now with no luck.

can you guys create an issue on the SickRage/SickRage github? maybe the dev can figure out why it's not recognizing it needs to drop the old commit number

 

[Ray Milyard]

can you guys create an issue on the SickRage/SickRage github? maybe the dev can figure out why it's not recognizing it needs to drop the old commit number

To be honest I am not sure how to do that. Even time I post there it gets closed without any help.

 

[Joshua Parker Ruehlig]

To be honest I am not sure how to do that. Even time I post there it gets closed without any help.

when did you try? that repo is only a few weeks old.

 

[sp3cialk]

Think I fixed mine. Stopped SR, Edited the config.ini and removed the cur_commit_hash = xxxx Saved and restarted SR. I'd get the notice it wasn't aware of version so I needed to update. Ran through it twice and now if I check for update no error.

Currently showing

Code:

SR Version:    BRANCH: (master) / COMMIT: (81aa99c0b4bd39fbf333decd6e4f6c155d9401ef) 

 

[Ray Milyard]

when did you try? that repo is only a few weeks old.

I tried today. Issue was closed ASAP saying on old repo. Said need to change it and or contact FreeNAS. Kinda not sure what they need from me.

 

[INCSlayer]

i updated the

did you update the plugin or do the steps people are posting? can you guys also confirm you can ping github.com?

the steps i took was
1. backup the database
2. shutdown sickrage from the sickrage management page
3. turn it of from the plugin page in freenas
4. update from the plugin page in freenas
5. turn it back on

and after that i have the issue

 

[Joshua Parker Ruehlig]

I tried today. Issue was closed ASAP saying on old repo. Said need to change it and or contact FreeNAS. Kinda not sure what they need from me.

lol, you're on the new repo, just the old commit number isnt getting cleared. not sure why mine worked, but you guys updated later then me on the old repo. maybe eche0n did something to store the commit more permanently.

 

[Ray Milyard]

Think I fixed mine. Stopped SR, Edited the config.ini and removed the cur_commit_hash = xxxx Saved and restarted SR. I'd get the notice it wasn't aware of version so I needed to update. Ran through it twice and now if I check for update no error.

Currently showing

Code:

SR Version:    BRANCH: (master) / COMMIT: (81aa99c0b4bd39fbf333decd6e4f6c155d9401ef) 

Just did the same. Looks like with you now also.

 

[INCSlayer]

i did the same thing that @sp3cialk and it seems to have worked

Code:

 SR Version:    BRANCH: (master) / COMMIT: (81aa99c0b4bd39fbf333decd6e4f6c155d9401ef)

 

[Joshua Parker Ruehlig]

i did the same thing that @sp3cialk and it seems to have worked

Code:

 SR Version:    BRANCH: (master) / COMMIT: (81aa99c0b4bd39fbf333decd6e4f6c155d9401ef)

great, at least we have a workaround.