My sonarr shuts down with no prompting from me, occasionally. I believe it’s triggered when it checks for an update, and there is one. I’ll come to my ubuntu machine and find that there is a sonarr update in my software updates waiting to be installed. The logs seem to show nothing. They just stop. Running 14.04 and all the updates from Sonarr.
Disable respawn in the Upstart config, it causes the upgrades to fail, the wiki has been updated to reflect this issue: https://github.com/Sonarr/Sonarr/wiki/Autostart-on-Linux
Thanks. Strangely, I had done that before.
Respawn is already commented out.
Which version of mono?
3.6.0 according to mono -V
Knowing what its doing when it crashes would be helpful, but its also worth updating to mono 3.10, its available in our debian repo.
oh i thought that updated automatically now. Sorry how do I install that? I’ll try to note the time and get the logs next time it crashes… for right now i’m trying to figure out how to get write access to this newly installed internal drive that I ripped out of my popcorn hour.
sudo apt-get update and sudo apt-get upgrade should do it
Hey Markus
I run that all the time. Just ran it 30 minutes before I looked at the mono version. Wonder what’s up with all these differences.
Its in our repo: https://github.com/Sonarr/Sonarr/wiki/Installation#debianubuntu
Did you compile 3.6 before?
I followed your guide on installing. That’s all I know. 
Next question: Do I navigate to a mono folder and do a git pull?
No, you don’t want the source, you want it compiled. Having mono 3.6 sounds like you did compile it though and either 3.10 isn’t installed or 3.6 is taking preference.
Yeah I guess I’m confused. Are you saying I should install everything over again? That page mainly talks about installing everything from the beginning, and the link to “building your own” mono goes to a page about 3.6.
I have been seeing the updates relating to mono when I do my overall system updates. Not sure why 3.6 is still running in that case.
mono 3.10 is included for x86/x64 in our repo (mirrored from Xamarin’s), for other platforms you may have to compile it yourself: http://www.lovesmesomecode.com/20130719-compiling-mono-3-in-ubuntu/
mono 3.10 is available as a pre-compiled package for Ubuntu and Debian (and other debian platforms). This is a recent change, last 30 days or so. Sounds like 3.6 was compiled previously and is preferred over 3.10 coming from the repo, in which case you need to remove 3.6.
which mono should show you where its coming from, 3,10 on my system is coming from /usr/bin/mono
Thanks for the help. I have an opt/mono folder so I’m using that, although I also had a mono 3.6 folder in my home directory.
I got an error when I tried the git commands, “could not create work tree dir ‘mono’” and the “permission denied” for the second one. I overcame this with sudo. I hope that wasn’t a bad sign.
which mono also showed min at /usr/bin/mono
I got more errors during the ./autogen.sh step, so I went into the libgdiplus directory where it started running until I got another error, which I overcame with the sudo command again, and I got several messages saying “you should put blah blah and in blah blah”. And then this at the end:
configure: error: Package requirements (cairo >= 1.6.4) were not met:
No package 'cairo' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables CAIRO_CFLAGS
and CAIRO_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.trying in both the libgdiplus directory and the opt/mono directory:
typing make: make: *** No targets specified and no makefile found. Stop.
sudo make install: make: *** No rule to make targetinstall’. Stop.`
regarding the make errors, tried this: https://github.com/nathanb/iws-snippets/issues/9 but did not work