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?
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.
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.
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.
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.
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.