Alright so I know a lot of people want Sonarr as a FreeNAS plugin. Well guess what? It’s pretty damn easy to setup manually. I’ll walk you through the unix commands, from there you’re on your own. Ready? Crack dem knuckles!
(NOTE: I did this with the latest version of FreeNAS (9.2.1.9))
Create a new jail in FreeNAS, just the default settings, give it a name and create.
Ok 2 options for this. Either SSH into your FreeNAS box, run ‘jls’ to find your jail #, and then ‘jexec # csh’ OR you can shell into your jail via the jails tab in the FreeNAS GUI. Either way you need to be sitting at a shell for your jail. The next steps are commands to run.
Stop, and then start the jail in FreeNAS GUI. Hit up http://:8989 Should be good to go.
Notes: line 19 you will just be typing into a text editor, it’s not a command. Line 11 has a dot ‘.’ before the slash, you need that in the command. Hopefully I didn’t forget a random step I did. Let me know if it works.
Try my rc.d method again, but this time run: chmod 777 /etc/rc.d/run_drone After you make the script, or if it still exists just run that command and restart the jail. I forgot to add that step and it may be the cause of the issue. Let me know if it works so I can update the OP.
Edit: DEFINITELY don’t forget the ‘&’ at the end for the rc.d script, that can cause a no-boot. It’s easily fixable, but just to save you hassle up front
Appreciate the great walk through. I am using the same version of FreeNAS as you, but when I run the pkg install command, I get an error that no valid repository was found. Did you run in this as well, or did I miss something?
I’m going to assume the system user didn’t have rights to run the rc.d script then and by 777 nuking it it’s allowed the system to finally call it properly.
edit /usr/local/etc/pkg/repos/FreeBSD.conf
make the url http:// only (not pkg+http)
after this “pkg update”
"upgrade pkg"
edit the FreeBSD.conf file again and re-add the pkg+http part
apologies i can’t be more help i fixed it quite a while ago.
Awesome! Yeah I was writing the steps from memory and forgot that one, but it’s now added to the OP. One thing I’m going to work on now is crash detection and relaunch. Sonarr crashed on me after a few days and there’s no way to know until you access it. Otherwise I’m loving it, huge upgrade from Sickbeard.
Awesome, thanks! I see its linked from the installation page
Anything in the logs? If it was during an update (logs something similar to Starting NzbDrone.Update) then its usually a permissions or related to starting mono up again.
I can’t remember when exactly it crashed, so I can’t find it in the logs at the moment. Next time I’ll check the logs when I bring it back up and let you know.
Mine tends to hang crash on first library scan and most/all subsequent scans. Either that or i am being impatient. small scans of individual shows don’t cause it to hang/crash.
Make sure you’re on the latest release, we recently fixed an issue with DB locks. Also check mediainfo for an update, if mediainfo wasn’t already scraped for a file it will be on rescan (we had some issues with an old version on Windows).
Ah I thought I was up to date, I was actually a few versions behind. All updated now. The GUI update doesn’t work for me, but just removing the old Nzbdrone directory and extracting the new version in works.
In what way doesn’t it work? It needs re-write permissions and has to be able to spawn an update process, which will terminate the existing version and spawn another in its place.
Updates is a pretty important piece, so we’d really like to solve it if we can.