[FreeNAS 9 Plugins] - SAB / SB / CP / HP / Maraschino / HTPC / Mylar / LL / Gamez

[AirborneTrooper]

I'll try to download that same movie again and see if it works.

UPDATE: That fixed it! Thank you very much for the help!

 

[Joshua Parker Ruehlig]

I'll try to download that same movie again and see if it works.

UPDATE: That fixed it! Thank you very much for the help!

welcome, thanks for pointing out the missing line from my blog!

 

[AirborneTrooper]

No problem, but as a suggestion, you might want to put a change log at the top of your blog post so people know you have made changes.

 

[Joshua Parker Ruehlig]

No problem, but as a suggestion, you might want to put a change log at the top of your blog post so people know you have made changes.

that sounds like a good idea... but im too lazy/have other stuff to do, lol

 

[neto_hugo]

Joshua a curiosity ...

Seeing the attributes in /var/db/sickrage/config.ini I found a setting maybe a little strange ...

Code:

 root_dir = 0 | /mnt/media/video/tvshow

in your configuration also has this '0|'? Should not be only /mnt/media/video/tvshow?

Another thing, when watch the log of the SR post-processed script, I stumbled several times with the following information:

Code:

[INFO] :: MAIN: Checking if git needs an update
[INFO] :: MAIN: There is a newer version available (you're 16 commits behind)
[INFO] :: MAIN: nzbToMedia Version: ab24081e30171539d0b65283b62d87d0d6294a12 Branch: master (FreeBSD 9.1-RELEASE)

Would recommend updating nzbToMedia? If so, how do I proceed?

Thanks for your help ....

 

[Joshua Parker Ruehlig]

Joshua a curiosity ...

Seeing the attributes in /var/db/sickrage/config.ini I found a setting maybe a little strange ...

Code:

 root_dir = 0 | /mnt/media/video/tvshow

in your configuration also has this '0|'? Should not be only /mnt/media/video/tvshow?

Another thing, when watch the log of the SR post-processed script, I stumbled several times with the following information:

Code:

[INFO] :: MAIN: Checking if git needs an update
[INFO] :: MAIN: There is a newer version available (you're 16 commits behind)
[INFO] :: MAIN: nzbToMedia Version: ab24081e30171539d0b65283b62d87d0d6294a12 Branch: master (FreeBSD 9.1-RELEASE)

Would recommend updating nzbToMedia? If so, how do I proceed?

Thanks for your help ....

not sure about the sickrage config, I usually don't mess with that directly. I'm sure the dev could explain what it means on his forum.
To update nzbToMedia run..

Code:

cd /usr/local/share/nzbToMedia && git pull
chown -R media:media /usr/local/share/nzbToMedia

Before you do this you might want to check his changelog to make sure you don't need to change anything in your config, I think things have been pretty stable lately though.

 

[malum-in-se]

Joshua,

I will be brief. I apologize, I've seen the answer for this before, but due to the length of these threads I can't find it. I spent an hour searching google, and another searching this forum to no avail.

Sickrage web GUI says it doesn't know the version and there is an update available. Normally I wouldn't worry about it, because if you have something that works, it's about 50/50 that an upgrade can break it. The reason I'm looking to upgrade is that while Sickrage is doing an OK job finding epsiodes, and the download, sorting and renaming is working, it's not nearly as effective as Sickbeard usually is finding back episodes. I also know that with all the support you give for freenas and the plugins, you don't support the specific plugin issues, which I completely understand, and am appreciative of the support you give.

Looking at my Sickrage logs, it's kicking up a "no RID or search term found" error on most (approximately 75%) of the episodes it's looking for. I went through some Sickrage forums and found that they identified the issue and there were some Github fixes posted. They were fixes to some of the python scripts, which I generally don't mess with myself, as I'm more prone to break the complete package, than fix the individual program. Thus I wanted to see if upgrading Sickrage fixed the problem.

So my question is: 1. The no version found, "click to upgrade", do I just ignore that? I installed Sickrage from the repository you linked, about 2 weeks ago. Am I on the most current version, and if so, should I just ignore the notice on the GUI? 2. If I am not on the most current GUI, or if I do reach a time i want to upgrade, what is the proper way to do it without breaking the install instructions of yours I followed? Do I do it from the GUI or from the command prompt wihin the jail? 3. If I do it from within the jail, what are the appropriate commands? Sorry for a basic question, I'm still learning packages and dependancies and have about a 50% success rate upgrading from the prompt.

As always, thanks for your time.

 

[Savell Martin]

Hey Josh,

Being cheeky and wondering if you have had a chance to look at Sonarr?

 

[Joshua Parker Ruehlig]

Hey Josh,

Being cheeky and wondering if you have had a chance to look at Sonarr?

It's moving it's way up the list. Planning on looking at it soon.

 

[Joshua Parker Ruehlig]

Joshua,

I will be brief. I apologize, I've seen the answer for this before, but due to the length of these threads I can't find it. I spent an hour searching google, and another searching this forum to no avail.

Sickrage web GUI says it doesn't know the version and there is an update available. Normally I wouldn't worry about it, because if you have something that works, it's about 50/50 that an upgrade can break it. The reason I'm looking to upgrade is that while Sickrage is doing an OK job finding epsiodes, and the download, sorting and renaming is working, it's not nearly as effective as Sickbeard usually is finding back episodes. I also know that with all the support you give for freenas and the plugins, you don't support the specific plugin issues, which I completely understand, and am appreciative of the support you give.

Looking at my Sickrage logs, it's kicking up a "no RID or search term found" error on most (approximately 75%) of the episodes it's looking for. I went through some Sickrage forums and found that they identified the issue and there were some Github fixes posted. They were fixes to some of the python scripts, which I generally don't mess with myself, as I'm more prone to break the complete package, than fix the individual program. Thus I wanted to see if upgrading Sickrage fixed the problem.

So my question is: 1. The no version found, "click to upgrade", do I just ignore that? I installed Sickrage from the repository you linked, about 2 weeks ago. Am I on the most current version, and if so, should I just ignore the notice on the GUI? 2. If I am not on the most current GUI, or if I do reach a time i want to upgrade, what is the proper way to do it without breaking the install instructions of yours I followed? Do I do it from the GUI or from the command prompt wihin the jail? 3. If I do it from within the jail, what are the appropriate commands? Sorry for a basic question, I'm still learning packages and dependancies and have about a 50% success rate upgrading from the prompt.

As always, thanks for your time.

Hmm, I doubt SickRage and SickBeard would perform differently finding its backlog. It just depends on what nzb / torrent sources you have for each of them. If that bug was fixed, and the commits were pulled into the master branch then doing the in-app upgrade would fix the issue.

1) That warning means the SickRage source you're running isn't a git repo. So, it wants to do a fresh pull of the source files from github and then it'll maintain it's version file in a text file. Clicking this will get you the current latest source, then it'll automatically self-update daily, unless you disable it. It should be fine, auto-updates occasionally break things so some people choose to disable them.

2) The in-app update should work fine. After clicking to upgrade, on either let auto-update run, or disable them and manually update when you feel like it. The steps I posted should be compatible unless SickRage/nzbToMedia change something drastically.

3) You don't need to do it from the jail, use in-app upgrading for SickRage+CouchPotato (which pulled the latest source during initial setup).
Transmission and SabNZBd you upgrade from FreeNAS WebUI > Plugins > Installed tab.
For nzbToMedia you do this https://forums.freenas.org/index.ph...htpc-mylar-ll-gamez.16200/page-54#post-172849

 

[malum-in-se]

Hello,

Tried upgrading from the GUI, it broke it. Have tried resetting the jail, actually even reset the NAS. No love, all I get when I try to go to GUI is:
Traceback (most recent call last):
File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/tornado/web.py", line 1313, in _execute
result = self.prepare()
File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/tornado/web.py", line 2002, in prepare
raise HTTPError(self._status_code)
HTTPError: HTTP 404: Not Found

I will reinstall and post back here with anything I learn.

 

[Joshua Parker Ruehlig]

Hello,

Tried upgrading from the GUI, it broke it. Have tried resetting the jail, actually even reset the NAS. No love, all I get when I try to go to GUI is:
Traceback (most recent call last):
File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/tornado/web.py", line 1313, in _execute
result = self.prepare()
File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/tornado/web.py", line 2002, in prepare
raise HTTPError(self._status_code)
HTTPError: HTTP 404: Not Found

I will reinstall and post back here with anything I learn.

The below commands should get you a fresh set of source without having to go through all the trouble of re-installing.

Code:

service sickrage onestop
rm -r /usr/pbi/sickrage-amd64/share/sickrage/SickRage
cd /usr/pbi/sickrage-amd64/share/sickrage && git clone git://github.com/SiCKRAGETV/SickRage.git
chown -R media:media /usr/pbi/sickrage-amd64/share/sickrage/SickRage
service sickrage start

 

[Joshua Parker Ruehlig]

@malum-in-se
See the last post, unless you wanted to reinstall everything again to learn.

 

[malum-in-se]

Hello Joshua,

Thanks for the additional guidance. I followed those steps, and I'm still getting the same result when I try to long in at the web GUI. Any other ideas on what might work?

 

[Joshua Parker Ruehlig]

Hello Joshua,

Thanks for the additional guidance. I followed those steps, and I'm still getting the same result when I try to long in at the web GUI. Any other ideas on what might work?

maybe the master branch is broken. I'll test updating a fresh install.

 

[malum-in-se]

If you have any interest, I've got the log file up of when the original upgrade went off the rails, let me know if you'd like a copy. I'm going to save my config files and reinstall from scratch.

 

[Joshua Parker Ruehlig]

If you have any interest, I've got the log file up of when the original upgrade went off the rails, let me know if you'd like a copy. I'm going to save my config files and reinstall from scratch.

Unless you have a reason for installing everything from scratch, you could just un-install SickRage, and delete it's data-directory then re-install and reconfigure SickRage.

 

[malum-in-se]

Uninstalled the sickrage plugin. then reinstalled the 9.3 PBI I had previously downloaded and it worked. Went to fire it up up and got this from the command line:

service sickrage start
Starting sickrage.
Your database version (42) has been incremented past what this version of SickRa
ge supports (41).
If you have used other forks of SB, your database may be unusable due to their m
odifications.
/usr/local/etc/rc.d/sickrage: WARNING: failed to start sickrage

Any way just to reinstall sickrage without having to start from scratch on the jail?

Before uninstalling I saved all of my config files, to see if I could get away without having to to re-enter all that info. However, when I tried to fire it up above, I did that before I had copied over any configs. The error above came back from a complete virgin reintall of sickrage.

 

[malum-in-se]

I think we just posted simulataneously. I didn't specifically delete the data directory. What is the normal path of that directory so I can make sure I'm nuking the correct one. I will try that.

 

[Joshua Parker Ruehlig]

I think we just posted simulataneously. I didn't specifically delete the data directory. What is the normal path of that directory so I can make sure I'm nuking the correct one. I will try that.

/var/db/sickrage

1) Stop sickrage
2) rm -r /var/db/sickrage
3) start sickrage

I just updated a fresh Sickrage install and it worked, so either something got screwed up in your sickrage config/database, or maybe the webroot "/sickrage" we set is causing an issue.