Running Sonarr 2.0.0.3645 on FreeNAS (FreeBSD), as a plugin in its own jail. Apart from the often problems I have (which I attribute to mono, and will fix later when I have the time) it’s all pretty good.
I was wondering if there was a way to control the automatic tasks - when they run, or if I can disable certain ones altogether?
I would like to turn off the automatic application updates. Usually not a problem, but I am running into some issues with the latest update; (well, I was going to write the version here but things have crashed again on me).
Since trying to apply that update Sonarr has become extremely fragile and often crashes. I thought it was the update itself, not working properly and crashing but maybe it isn’t. Regardless, I’d like to disable the application from running this update until I can determine the cause of any other problems and address them, before I introduce possible other problems with the update.
Hmm … blast!, as I am writing this post I had restarted Sonarr and it didn’t attempt the update so it stayed stable and began downloading episodes. However, it is now fully unresponsive. Will do an OS update - I just saw the sticky about mono problems being fixed in a newer kernel - hopefully this includes the kernel used in FreeBSD / FreeNAS.
But, what about under System > Tasks, Application Update? Is this just checking for the update?
It’s being very temperamental for me tonight. It does this on occasion and then will just come good. As I said earlier, it’s FreeNAS 9.2.1.9 (older version, yes), and later I will upgrade this to 9.3 I haven’t looked but just hope there’s a kernel update in that, and maybe something else - which might help with mono, as I feel this guy is probably the culprit to instability. Thoughts? Anyone else have Sonarr running on FreeNAS with relative happiness?
I also thought about RAM too, I’m kinda cutting it close with that too. When I checked earlier, I was getting as low as 240MB free, out of 10GB - so, maybe running out of RAM or not liking swapping or something might be an issue.
Couple of things for me to cover off but I’ll start with the FreeNAS 9.3 upgrade and go from there…
Yeah, exactly, it will check for the update, but not install it when its disabled.
I don’t think the kernel would have the same updates as its two different systems, BSD vs Linux, but it may help. Also worth making sure you have a recent version of mono 3.10 or later.
The biggest issue with BSD and mono is mono doesn’t officially support BSD, so it takes someone working on the BSD implementation to fix some issues.
root@sonarr_1:/ # mono --version Mono JIT compiler version 4.2.1 (Stable 4.2.1.124/39edf24 Thu Jan 7 20:10:39 UTC 2016) Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com TLS: __thread SIGSEGV: altstack Notification: kqueue Architecture: amd64 Disabled: none Misc: softdebug LLVM: supported, not enabled. GC: sgen
So … there’s that. I can see there’s the ability to change logging verbosity in the UI - does this log to a single file? Do you know the path in BSD? Probably also worth me tailing that to see what’s going on when it becomes unstable.
Thats the latest version of mono, which still has at least one issue in it (Unable to find processes properly).
The log file location is in the AppData directory, which is shown in the UI on System: Status. Probably best to capture the standard output and standard error information from the console as well, since if mono fails Sonarr is likely to be unable to log anything.