Crash after Centos 7 update

Sonarr version (exact version): latest downloaded from http://update.sonarr.tv/v2/master/mono/NzbDrone.master.tar.gz
Mono version (if Sonarr is not running on Windows):
Mono JIT compiler version 2.10.8 (tarball Mon Jan 4 14:05:48 UTC 2016)
Copyright © 2002-2011 Novell, Inc, Xamarin, Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: debugger softdebug
LLVM: supported, not enabled.
GC: Included Boehm (with typed GC and Parallel Mark)
OS: Centos 7
((Debug logs)):
http://hastebin.com/bucomigepi.lua
Description of issue:

Sonarr was running fine before a system wide YUM update which seems to have updated mono packages. After the update, Sonarr no longer works. The mono process is seen in “ps -A” but the service is not bound to port 8989 and is therefore not accessible. Looking in the logs, I have attached the stack trace available at http://hastebin.com/bucomigepi.lua

The same stacktrace is produced if Sonarr is manually started. Additionally, I have opened a ticket on Github: https://github.com/Sonarr/Sonarr/issues/1504

I have tried to reinstall sonarr from scratch (deleted everyhting then followed the instructions of https://github.com/Sonarr/Sonarr/wiki/Installation-CentOS-7) but I get the same behavior.

Mono 2.10 is WAY too old, I guess it didn’t ‘update’ mono but rather ‘downgraded’ it back to the stone age.

Well good catch!!!

The EPEL repo was somehow assigned higher priority (due to a restored system backup) than the Mono Repo (the official one) and consequently 2.10 was installed instead of 4.6.1…

Im wondering why 2.10 is still available on EPEL? Anywahs not my problem and certainly not Sonarr’s…

Now all works fine! THanks Taloth for the catch!

Kudoes goes to you for actually filling in the requested information :slight_smile: It’s a rarity.

Thanks Taloth,

2 things I notice often, especially on development systems:

  1. People do not provide the basic information (version numbers, hardware config, OS, system specifics, etc). This makes initial troubleshooting almost impossible outside of a wild guess…

  2. People do not follow up on their own threads. This is most irritating since you find dozens of threads on the internet where people have had the exact same issue, and that they reply with is either nothing (no post resolution feedback at all) or worst (almost insulting to others) with an answer like “its all good now it works”…

I sometimes ask stupid or obvious questions (sometimes the answers are so close you dont see them) but I always try to make it easier for others to help me.

BTW Sonarr is ROCK solid now!

Ugh, I had that today at work, last reply on some thread about TFS was “It’s working now, our ICT department made a configuration error.”. But hey, I figured it out.

Awesome that it’s working stable now, that’s the way we like it. Stable, automated.

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