sigh Looks like I lied, SEGV overnight again. Still running much better than it has though.
Is this patch only for the VM issues, or will this also help non-VM users?
I honestly don’t know. I just want to get this known issue out of the way, then we can look if there are other issues remaining.
Since most of the above users can still restart NzbDrone after it crashes - yall doing anything special to get it going again? I’m unable to start it again due to a ghost process still using the port. Already killed mono and tried fuser -k port/tcp etc… no luck:(
Debian 8
kernel 3.2.0-4-amd64
Mono 3.6
Hyper-V E5-2630v3 ( 6 cores assigned)
Hardware: Not virtual. Intel Pentium G2120
Distro: Ubuntu 14.04.2 LTS
Kernel: Linux server 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Sonar version: I think it was from May 21
Mono --version provides:
Mono JIT compiler version 3.10.0 (tarball Wed Nov 5 12:50:04 UTC 2014)
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
Is there anything wrong with just setting up a cron for:
start nzbdrone
I mean, considering you can manually run that command over and over and it immediately outputs “Job is already running” if it is, or starts if it isn’t, couldn’t I just have that command run every minute or so?
Obviously not ideal, but is it an OK workaround? I’m no Linux guru.
Not a VM here.
Crashes hourly.
CPU i7-3770
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
Linux TVSHOWS 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Mono JIT compiler version 4.0.1 (tarball Tue May 12 15:39:23 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
Version 2.0.0.3154
Mono Version 4.0.1 (tarball Tue May 12 15:39:23 UTC 2015)
Currently trying to downgrade kernel.
and i broke it, tried to downgrade kernel, installed it rebooted. (SSH) wouldn’t change. Removed other kernels update grub, rebooted. Server never came back. Full reinstall in progress :’(
Not sure if you need another voice or not, but I too am having severe crashes on my physical server, where the entire thing goes after just a few minutes (much worse after the latest update).
Hardware: Intel Pentium G3258 (Dual Core)
Distro: Ubuntu 14.04.2
Kernal: 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Version: 2.0.0.3154
Mono Version: 4.0.1 (tarball Tue May 12 15:39:23 UTC 2015)
I tried to check on the error in the logs but all it stated was just Native stacktrace:, without any further lines.
1 Like
Did you try to downgrade your kernel yet from 52 to 46. I’ve tried unsuccessfully but apparently that’s the key.
I tried going down from 53 to 46 over the weekend and the system would just stall on bootup.
I also saw the drastically decreased stability after the last Sonarr update, to the point that I couldn’t run longer than 30 seconds most of the time.
I’ve since modified my upstart script to set a single core affinity:
exec taskset -c 0 mono --debug $DIR/NzbDrone.exe
This got me back to the levels of stability I was seeing before the update (12-36 hours of runtime before crashing)
I’ve put a simple entry into my cron.hourly that checks and starts Sonarr as needed. At least that way I’m not constantly starting it manually. It’ll get me by until -54 is released hopefully.
That is what i think i will have to do too. I pretty much screwed my machine twice trying to go down. What does the exec do?
exec is part of the upstart script itself. I just modifying the suggested upstart script provided with Sonarr and inserted the taskset: https://github.com/Sonarr/Sonarr/wiki/Autostart-on-Linux
Oh i see, sorry i was using this one:
Not sure how you managed to wreck your system badly enough that it required a re-install. You can just pick the correct kernel during grub bootup. Changing the default isn’t strictly required.
I’m waiting with overwhelming anticipation for -54…
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458618
Not sure, i’m headless and remote, so i will just wait, not a linux pro. Is this bug specifically related to mono per say? Or could it affect other applications? Just wondering because plex seems to also be dropping.
FYI I pulled the latest early testing builds from the kernel ppa.
All tested on a 14.04.2 trusty vm.
3.13.0-53.x was still crashing. (trusty-updates)
3.13.0-54.61 seems to work. (ppa)
lts-utopic:
3.16.0-38.30 was still crashing. (trusty-updates)
3.16.0-39.31 seems to work. (ppa)
Prolly could use someone versed in linux to try it out on a physical machine. But I take no responsibility if it utterly breaks your machine, coz these are early testing builds. Don’t blindly add the ppa, it gotta be pinned with low priority to avoid unwanted updates.
1 Like
Sonarr does self checks on startup to make sure it’s not already running and quits if it detects a process already running, so my cron is extremely simple:
cat /etc/cron.hourly/start-sonarr
#!/bin/sh
start nzbdroneMine is just:
*/1 * * * * /etc/init.d/nzbdrone start
@Taloth Im going to wait haha. Looking hopeful though.
Thanks @jrhelbert
I get an error unless I use the following to start Sonarr which doesn’t work with cron.
sudo start nzbdrone
It must be something to do with the user that Sonarr is running under or something.
Edit: Never mind, I figured it out!