Emby Crashes Status 134 After Update

[Jukari 1]

Environment:

ODroid XU4 with Dietpi

 

 

I had Emby working without a hitch two versions ago. I updated today to the latest version and it crashed with status 134. While attempting to repair it I wiped my configs... causing me to reload the entire OS and start from scratch. However even off a fresh install I get Status 134.

 

The service will start and run for about 20 seconds then fail with this error:

root@Emby-Droid:~# sudo service emby-server status
● emby-server.service - Emby Media Server
   Loaded: loaded (/lib/systemd/system/emby-server.service; disabled)
   Active: failed (Result: exit-code) since Fri 2017-10-27 18:52:02 BST; 18s ago
  Process: 3855 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS)
  Process: 3384 ExecStart=/usr/bin/emby-server start (code=exited, status=134)
 Main PID: 3384 (code=exited, status=134)

Oct 27 18:52:02 Emby-Droid emby-server[3384]: bea64000-bea85000 rw-p 00000000 00:00 0          [stack]
Oct 27 18:52:02 Emby-Droid emby-server[3384]: ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]
Oct 27 18:52:02 Emby-Droid emby-server[3384]: Native stacktrace:
Oct 27 18:52:02 Emby-Droid emby-server[3384]: Debug info from gdb:
Oct 27 18:52:02 Emby-Droid emby-server[3384]: mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb
Oct 27 18:52:02 Emby-Droid emby-server[3384]: =================================================================
Oct 27 18:52:02 Emby-Droid emby-server[3384]: Got a SIGABRT while executing native code. This usually indicates
Oct 27 18:52:02 Emby-Droid emby-server[3384]: a fatal error in the mono runtime or one of the native libraries
Oct 27 18:52:02 Emby-Droid emby-server[3384]: used by your application.
Oct 27 18:52:02 Emby-Droid emby-server[3384]: =================================================================

[Luke 37188]

Hi there, is there an Emby Server log? thanks.

[Jukari 1]

Attached are all the files I found in:

 

/var/lib/emby-server/logs

server-63644724463.txt

server-63644724083.txt

server-63644724643.txt

server-63644724787.txt

server-63644725149.txt

server-63644727090.txt

unhandled_39039d34-c128-4dc1-863b-dfe873fc4d37.txt

unhandled_e1f9fef5-3fb2-4674-98d7-ecbb075e09e9.txt

unhandled_e7111df7-13b2-4220-9194-aad563998046.txt

[Luke 37188]

Ok, I would like to point out that you've got the mono runtime 5.4 installed, and our highest supported version right now is 4.8.1. I would suggest rolling that back. Thanks.

[Jukari 1]

I'm not super Linux savy how do I roll a package back to an older one?

[tophershane 0]

It's definitely the mono version, I can recreate with mono 5.X+.  What distribution of Linux are you running and how did you install mono initially, or which instructions did you use to install Emby? 

[Jukari 1]

It was indeed the Mono version causing the problem. It was a huge pain to figure out a way to roll back Mono. So I'm leaving behind the fix action for the next person who runs into it (I found it in the forums but don't recall the commenter's name without searching. So here's the fix action from the anonymous source:

apt remove libmono-2.0-1 mono-utils mono-jay mono-devel  mono-runtime mono-runtime-sgen mono-mcs mono-complete
	
apt-get install -f mono-complete libmono-2.0-1=4.8.1.0-0xamarin1 mono-utils=4.8.1.0-0xamarin1 mono-devel=4.8.1.0-0xamarin1 libmonosgen-2.0-1=4.8.1.0-0xamarin1 libmono-2.0-dev=4.8.1.0-0xamarin1 libmonoboehm-2.0-1=4.8.1.0-0xamarin1 libmonosgen-2.0-dev=4.8.1.0-0xamarin1

[Luke 37188]

Thanks for the feedback.