Nzbdrone fails to start after mono update

Help & Support
1

Hello all,

Ive just updated MONO from 3.2.8 to 3.10 as it was a bit old, so i manually updated mono and it is now 3.10 which seems to work (ubuntu 14.04). However, now nzbdrone wont start, it gives me this msg:

[Info] Bootstrap: Starting NzbDrone - /opt/NzbDrone/NzbDrone.exe - Version 2.0.0.2152

  • Assertion at processes.c:2595, condition `mp’ not met

Stacktrace:

at <0xffffffff>
at (wrapper managed-to-native) System.Diagnostics.Process.ExitCode_internal (intptr) <0xffffffff>
at System.Diagnostics.Process.get_HasExited () <0x00033>
at (wrapper remoting-invoke-with-check) System.Diagnostics.Process.get_HasExited () <0xffffffff>
at NzbDrone.Common.Processes.ProcessProvider.ConvertToProcessInfo (System.Diagnostics.Process) <0x00163>
at NzbDrone.Common.Processes.ProcessProvider.GetCurrentProcess () <0x00013>
at NzbDrone.Common.Processes.PidFileProvider.Write () <0x00087>
at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext,NzbDrone.Host.IUserAlert,System.Action`1<NzbDrone.Common.Composition.IContainer>) <0x0016a>
at NzbDrone.Console.ConsoleApp.Main (string[]) <0x0007b>
at (wrapper runtime-invoke) .runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

mono() [0x4b3618]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f17f4280340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7f17f3ee0bb9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f17f3ee3fc8]
mono() [0x626d59]
mono() [0x626f5f]
mono() [0x6270a6]
mono() [0x6058c5]
mono() [0x606e53]
mono() [0x57f12e]
[0x401526a5]

Debug info from gdb:

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

Does anyone have any idea wth this is?

2

If you’re not running mono with --debug, please do. Drone is trying to get information on the current process and failing, which looks to be an issue with mono. Lots of people running 3.10 now, maybe one of them can shed the light on the issue.

3

I just tried running with --debug behind it but i get the same thing.
It says it dumped a core though, no idea where.

Aborted (core dumped)

To update i followed this doc: http://www.lovesmesomecode.com/20130719-compiling-mono-3-in-ubuntu/

FYI, mono -V says:

mono -V
Mono JIT compiler version 3.10.1 (master/2a14bc4 Tue Oct 21 21:47:05 CEST 2014)

4

It definitely looks like a problem with mono, I haven’t setup 3.10 on my test box yet, but I know others are using it successfully. Master is a WIP as far as I can tell, you’d be better off pulling the 3.10.0 tag and using that to build as it should be more stable. The latest commits show on going development: https://github.com/mono/mono/commits/master

5

I downgraded to Mono 3.6 and now everything is working again :slight_smile:

6

how do you downgrade? I couldn’t figure it out.

7

Compile from scratch with 3.6 and then make, make install.
Here: