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.