mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb

[simonk83]

Lots of frequent crashes with the latest version, logs say:

* Assertion: should not be reached at sgen-scan-object.h:90

(massive stacktrace omitted)

mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb
=================================================================
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.
=================================================================

Running on a Synology DiskStation.

[ethanopp]

+1 QNAP container station

[jkaberg]

@sparklyballs pretty sure this is due to the mono version (5.0.1.1), I'm now running another container with mono 4.6.2.16 which works just fine.

I noticed that only 5.0.1.1 is available from alpine repo.

[sparklyballs]

@jkaberg this image doesn't use alpine, it's based on ubuntu xenial.

[jkaberg]

ah right my bad. anyhow just letting you know in case you want to downgrade (or upgrade) 😄

[cron410]

Also seeing this issue on RancherOS

[MrBlaTi]

Also having that issue on Arch

[enchained]

I'm also having this, on Synology DSM 6. Could anyone suggest any solution, please? It's basically unusable right now in this state.

Ombi says mono version is 5.2.0.224 (tarball Tue Oct 3 19:49:47 UTC 2017). Tried to install mono 4.6.2.16 in the same container, but had no luck. Not sure how to better run this in another container with a different mono version, cause have not much experience with docker.

@sparklyballs any thoughts?

[aptalca]

May not be the solution you expect, but ombi 3 is currently in beta, doesn't use mono and will replace the mono version soon. You might want to switch now: https://hub.docker.com/r/lsiodev/ombi-preview/

[cron410]

That's what I switched to for compatibility with Organizr.

On Feb 4, 2018 12:16 AM, "aptalca" notifications@github.com wrote:

May not be the solution you expect, but ombi 3 is currently in beta, doesn't use mono and will replace the mono version soon. You might want to switch now: https://hub.docker.com/r/lsiodev/ombi-preview/

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/linuxserver/docker-ombi/issues/7#issuecomment-362881856, or mute the thread https://github.com/notifications/unsubscribe-auth/AC8KkycGS0Xqj_CJNlh46Tsf6szSYVprks5tRT0WgaJpZM4OUBH- .

[enchained]

Thanks! I was wary of the "do not use" warning, but at least that one works.

[CHBMB]

Container no longer based on mono. Going to close this.

[rochdev]

I get exactly the same behaviour using Ombi 3.0.3330 in Docker.

The image I use is linuxserver/ombi:91.

[rochdev]

Just tried with lsiodev/ombi-preview:53 which uses the develop branch for good measure, and I get the same behaviour.

[rochdev]

(I meant to post that in #9 actually so the behaviour I'm talking about is the server crashing after a search)

[aptalca]

@rochdev those are mono errors. How are getting exactly the same errors in the latest when it's no longer mono based? Post your logs

[CHBMB]

@rochdev Please explain how I my post above you when I closed the issue states that it's no longer based on mono how you're seeing the exact same issue, which was a problem with the mono version, when there's no mono in the image.

If you want to submit an issue, fine, but please use the template we provide and fill in all the information. If you don't we can't fix/look at it and we'll just close the issue.

[rochdev]

I opened a new issue with more information: https://github.com/linuxserver/docker-ombi/issues/32

Sorry for the confusion!