@Taloth, Updating mono and mediainfo didn’t stop crashes. I’m glad it worked for @macros.
I will attempt to figure out how to add the --debug switch to my startup items in Linux Mint.
Thanks!!!
Okay. Meanwhile I have to warn you, this is not going to be something easily fixed. (or it is easily fixed once we find out what the heck is going wrong in mono 
)
I’m also not able to do this alone so I’ll drag @markus101 in here as well.
might review the posting “Sonarr Crash after about 2 minutes”
I have this in my logs, pastebin links there too.
If it is mono 3.12.1, I have had pretty good luck. But that can run out?!?!
@Taloth and @markus101, I truly appreciate all your efforts.
I just donated $10 via PayPal. Have a great weekend.
I’ve been seeing the same error since moving back to Ubuntu Server 14.04 LTS from 14.10 a few weekends ago.
I found this thread yesterday and have upgraded mono and mediainfo to the latest from their PPAs instead of the ubuntu PPAs and since haven’t seen this error since. I previously couldn’t keep sonarr running for more than 15 min.
Previous (failing) Mono version:
mono --version Mono JIT compiler version 3.10.0 (tarball Wed Nov 5 12:50:04 UTC 2014) Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com TLS: __thread SIGSEGV: altstack Notifications: epoll Architecture: amd64 Disabled: none Misc: softdebug LLVM: supported, not enabled. GC: sgen
Previous (failing) MediaInfo version:
mediainfo --version MediaInfo Command line, MediaInfoLib - v0.7.67
Current (working) Mono version:
mono --version Mono JIT compiler version 3.12.1 (tarball Fri Mar 6 19:12:47 UTC 2015) Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com TLS: __thread SIGSEGV: altstack Notifications: epoll Architecture: amd64 Disabled: none Misc: softdebug LLVM: supported, not enabled. GC: sgen
Current (working) MediaInfo version:
mediainfo --version MediaInfo Command line, MediaInfoLib - v0.7.72
I’m running Linux Mint 17 based on Ubuntu
MediaInfo Command line,
MediaInfoLib - v0.7.72
Mono JIT compiler version 3.12.1 (tarball Fri Mar 6 19:12:47 UTC 2015)
Copyright © 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen
Crashes are less frequent but still occurring. I still don’t know where the mono debug log files will be written to.
Still haven’t seen this particular crash since updating mono and MediaInfo.
I was still seeing crashes, but I think I tied that to some issue with using SSL to connect to my deluge server. Since reverting the webui for deluge to non-SSL it’s been rock solid.
Still not able to complete an “update library” scan or rss scan. But I was kind of starting to wonder if it was some back end service we where using that might be dishing out bad data. Was thinking that Sonarr might be popular enough that its services might be getting hacked or datacenter attack. Guess github had a bought of it over the last week.
Its been hit and miss but still running enough to grab what I need.
Saw another post about a sqlite issue.
No it’s not a hack, those wouldn’t cause SIGSEGVs
We’re working with some users to identify what combination of mono and native libraries cause this. But it’s a tedious process since it’s something internal in mono or native dependencies, very hard to debug.
Keep the reports coming.
Looks like my luck ran out. Just like davlaw I haven’t been able to complete a library scan today without triggering this fault.
Hi sir. How can I just downgrade to the prior Sonarr version that didn’t have any issues?
Experiencing the same problems as others!
Please allow me to emphasis, this issue is likely caused by mono or a native library. Not guaranteed but likely.
Thus reverting to an older Sonarr version will probably not fix it (and isn’t possible without wiping the db)
I’m working with some guys trying to investigate this issue, but involves attaching low-level native debuggers to the mono process. So far the progress has been slow.
I’ve prepped a thread to start collecting important details about the various installs.
Best you can do is post the version information requested, if we can isolate what combination of libraries pose a problem.
See:
By now I’ve resorted to disabling parts of sonarr calling such native libraries.
“Yay, no crash, is it truely …?”… 5 minutes later SIGSEGV. “arghhhh”
I’m really thinking the team is doing nothing wrong, at least on purpose.
I have 2 systems running neither stable, but both linux spins. One that has been running since late part of 2013 and a new one just setup.
Has anyone determined if this is a linux only issue or does it affect both linux and win?
Looking at your post above they are all linux, its ran well for so so long.
If you can still read the post I pulled there is an sql injection that appears to affect sqlite3 and nix boxes.
@davlaw The exploit you linked isn’t even an exploit, not a sql injection either. it’s sending some tailored data to the sqlite3 cmdline. it’s like cmd < "Delete all my data" and then call it an exploit of cmd and executes the delete.
It’s not new either, late february. Bogus report imo.
And the issue is definitely linux only.
That said, the user system I was inspecting had at least one physical memory error. That system is now being put through a memory stress test before I’m going to look at it again.
Meanwhile I’m going over the reports again.
After performing a dist-upgrade, Mono updated the other day and I haven’t seen a crash yet.
/me crosses fingers
Mono JIT compiler version 4.0.1 (tarball Mon Apr 27 15:34:31 UTC 2015)
Copyright © 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen
1 Like
I managed to resolve this issue by switching from master to develop when installing sonarr, i.e.
echo “deb http://apt.sonarr.tv/ develop main” | sudo tee /etc/apt/sources.list.d/sonarr.list
Stable for a day now, fingers crossed.
OS: Linux Mint 13.2 cinnamon
bearjaws, the issues reported in this thread were related to a linux kernel issue. And that got fixed months ago. Pretty sure that upgrading sonarr won’t affect that.
If you’re still having issues, post a new thread with appropriate details, such as logs, kernel, mono, library versions etc.