SIGSEGV shortly after launch

Help & Support
1

Fresh install on Ubuntu 14.04.2 x64 following the directions on the wiki. Sometime between instantly and several minutes after launching it with “mono /opt/NzbDrone/NzbDrone.exe” I’ll get this error whether I’ve accessed the web interface or not (–debug not usually included but knew someone would ask for a log):

media@mediatank:~/.config/NzbDrone/logs$ mono --debug /opt/NzbDrone/NzbDrone.exe
[Info] Bootstrap: Starting NzbDrone - /opt/NzbDrone/NzbDrone.exe - Version 2.0.0.2850
[Info] MigrationLogger: *** Migrating data source=/home/media/.config/NzbDrone/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
[Info] MigrationLogger: *** Migrating data source=/home/media/.config/NzbDrone/logs.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
[Info] Router: Application mode: Interactive
[Info] OwinHostController: Listening on the following URLs:
[Info] OwinHostController: http://*:6503/
[Info] NancyBootstrapper: Starting NzbDrone API
[Info] SceneMappingService: Updating Scene mappings
[Info] HousekeepingService: Running housecleaning tasks
[Info] Database: Vacuuming database
[Info] Database: Database Compressed
Stacktrace:

Native stacktrace:

    mono() [0x4b3f7c]
    mono() [0x50c30f]
    mono() [0x423637]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f56ef75a340]
    [0x40d16b80]

Debug info from gdb:

Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.

Aborted (core dumped)

I managed to get it to stay running long enough to quickly get to the settings menu and enable trace logging. Glancing through the file I don’t see anything that would be too helpful but just in case it’s available here. I’m not sure where the core dump file is but if someone can point me to it I can try uploading it as well.

2

Which version of mono?

Nothing much in the logs as you mentioned, haven’t seen it happen that quickly on start up, but it could be as soon as it starts running jobs.

3

Packages chosen by apt were 3.10.0-0xamarin2, output of 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

I did manage to find the core dump in /var/crash. It’s a 14MB zip file (115MB extracted with the memory dump) but I can PM you the link if it’d help.

edit: Messing around in gdb a bit, got this:

(gdb) mono_backtrace 15
#0 0x401c3c09 in  Marr.Data.DataMapper:SetSqlMode (System.Data.Common.DbCommand) + 0x39 (0x401c3bd0 0x401c3c1b) [0x9db730 - NzbDrone.exe]
#1  0x00007ffff635c0e8 in ?? ()
#2  0x00007ffff635c0e8 in ?? ()
#3  0x00007ffff6215400 in ?? ()
#4 0x401c3aac in  Marr.Data.DataMapper:get_Command () + 0x6c (0x401c3a40 0x401c3ac8) [0x9db730 - NzbDrone.exe]
#5  0x0000000000000000 in ?? ()

So maybe some kind of database snag?