Debugging Sonarr Launch Issue - OS X 10.11.1 Public Beta

Hello,

I’m having issues getting Sonarr to launch - it won’t. Every time I attempt to start it, it prompts me to download the Mono framework (which is already installed and accessible in the command line). After that, it just won’t start at all.

I would start Sonarr in debug mode to see if there’s any telling output, but I can’t figure out the proper command to start it. The app is install with homebrew cask, FYI. I also don’t see any logs in the .config/NzbDrone directory. There is a monoInstall.log file, which I’ve dumped here. Looks like everything installed properly, though.

Any tips for me to figure out what the issue is here?

Which version of mono is installed? 32 or 64 bit?
Does the ~/.config/NzbDrone exist?

$ mono --version gives me

Mono JIT compiler version 4.2.0 (Stable 4.2.0.179/a224653 Fri Sep 25 17:15:20 EDT 2015)

64 bit, and yes that directory exists.

Where did you install mono from?

The latest official version of mono on their site is: 4.0.4 SR 4 El Capitan hotfix (4.0.4.4) http://www.mono-project.com/download/#download-mac

Try removing the existing version on mono and installing the version from their site.

The homebrew cask install method does upgrade to 4.0.4 (which includes a fix specifically for El Capitan, you just have to upgrade homebrew-cask first.

I believe the procedure is:

brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup
brew cask update
brew cask install mono-mdk

When my machine boots up, and Sonarr starts, Sonarr prompts me to download mono every single time, so I’m guessing I got mono straight from that prompt.

The Sonarr website has a 4.2.1 specifically for El Capitan that I assume was released after the El Capitan hotfix (4.0.4.4). Which would you recommend I install? Stick with the older 4.0.4.4?

I’ll try removing and reinstalling tonight when I get home.

I completely removed mono, installed via the homebrew cask install method recommended by Nelluk, came out with version 4.0.4.

I ran Sonarr after that, got the same ‘install mono’ prompt. Cancelled out of that and attempted to run, no luck.

Sorry for delay, since mono appears to be working there are a couple options we can try here:

  1. Grab the non-app release for OS X and try running Sonarr
  2. Run NzbDrone.exe in the OS X app via mono.

In both cases you will need to start Sonarr via terminal with mono --debug /path/to/NzbDrone.exe where /path/to is the proper path.

For #1 the path will be wherever you extract the tar.gz: https://download.sonarr.tv/v2/master/latest/NzbDrone.master.osx.tar.gz

For #2 the path will be inside the Sonarr.app, which will likely be: ~/Applications/Sonarr.app/Contents/MacOS/ assuming Sonarr.app was installed to your user’s Applications, or /Applications/Sonarr.app/Contents/MacOS/ if it was installed to the system’s Applications.

I downloaded Sonarr via homebrew cask. The commands I used at the time were:

brew cask install --appdir="/Applications" sonarr
brew cask install --appdir="/Applications" sonarr-menu-helper

The alias in my Applications folder points to:

/opt/homebrew-cask/Caskroom/sonarr-menu-helper/2.2/Sonarr.app/

Neither of the two folders you mentioned above nor the one I give above have NzbDrone.exe in those directories.

I uninstalled via brew cask (both sonarr and sonarr-menu helper), downloaded the link you gave above to the non-app release. Ran with mono in the command line. Voila - it works.

I then install Sonarr using the normal instructions:

brew cask install sonarr

And that works as well.

So I’m guessing it was the installation via brew cask either with the --appdir flag or the combination with the menu helper?

Anyway, thanks for the help. I’ll open another thread if something else pops up.

Interesting, glad to hear its working, thanks for letting us know!

I’m having this same issue, Sonarr just will not launch at all. Mac Mini running OSX 10.8.5.

Simple app install, won’t launch and just dies silently. Service (or whatever) is actually running though and I have to quit it from Activity Monitor.

Homebrew install behaves exactly the same.

Not sure what I should do… any suggestions appreciated!

I think my issue was related to the non-standard homebrew installation and/or using OS X 10.11.1 Public Beta. Perhaps it might be better to start a different thread since neither of those apply to your situation.

Ah ok… will do!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.