Emby bug or my system ?

[Muad 0]

 989 16115 0.0 1.4 374604 232648 - TNJ 8:22AM 1:18.00 /usr/local/bin/mono /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server (mono-sgen)

This PID is unkillable on my freebsd server! 

Have tested kill -9 and kill -19 

My setup:
FreeBSD hq.thunder.dome 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64

the emby server is running inside a iocage.
When trying too soft reset the jail it gets Killed, and no luck stopping the jail either.

This is a recurring problem on the server and it seems like hard reset of the freebsd is the only thing that can get it up and running again 

 

[Luke 37090]

Hi, welcome, sorry to hear about this. can you please provide an emby server log from this timeframe? instructions are here:

 

https://emby.media/community/index.php?/topic/790-how-to-report-a-problem/

 

Thanks !

[Muad 0]

I figured out why it happend. 
 

2016-10-04 14:59:09.5240 Error HttpAsyncTaskHandler: Error occured while Processing Request: Write failure

        *** Error Report ***

        Version: 3.0.5972.0

        Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server

        Operating system: Unix 10.3.7.0

        Processor count: 2

        64-Bit OS: True

        64-Bit Process: True

        Program data path: /var/db/emby-server

        Mono: 4.2.3 (Stable 4.2.3.4/832de4b Tue Sep 27 03:41:38 UTC 2016)

        Application Path: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe

        Write failure

        System.IO.IOException

          at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x919f40 + 0x0013c> in <filename unknown>:0 

          at SocketHttpListener.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) <0x919de0 + 0x0009a> in <filename unknown>:0 

          at SocketHttpListener.Net.ResponseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) <0x917000 + 0x001d7> in <filename unknown>:0 

          at ServiceStack.Formats.HtmlFormat.SerializeToStream (IRequest request, System.Object response, IResponse httpRes) <0xc2a000 + 0x00d05> in <filename unknown>:0 

          at ServiceStack.HttpResponseExtensionsInternal.WriteErrorToResponse (IResponse httpRes, IRequest httpReq, System.String contentType, System.String operationName, System.String errorMessage, System.Exception ex, Int32 statusCode) <0xc288d0 + 0x0021f> in <filename unknown>:0 

          at ServiceStack.ServiceStackHost.OnUncaughtException (IRequest httpReq, IResponse httpRes, System.String operationName, System.Exception ex) <0xc28100 + 0x002a7> in <filename unknown>:0 

          at ServiceStack.HostContext.RaiseUncaughtException (IRequest httpReq, IResponse httpRes, System.String operationName, System.Exception ex) <0xc280b0 + 0x00042> in <filename unknown>:0 

          at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse (IResponse response, System.Object result, ServiceStack.Web.ResponseSerializerDelegate defaultAction, IRequest request, System.Byte[] bodyPrefix, System.Byte[] bodySuffix) <0x912c30 + 0x0112a> in <filename unknown>:0 

          at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse (IResponse httpRes, IRequest httpReq, System.Object result, System.Byte[] bodyPrefix, System.Byte[] bodySuffix) <0x912450 + 0x002a9> in <filename unknown>:0 

          at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse (IResponse httpRes, IRequest httpReq, System.Object result) <0x9120f0 + 0x00023> in <filename unknown>:0 

          at ServiceStack.Host.RestHandler+<>c__DisplayClass5.<ProcessRequestAsync>b__0 (System.Object response) <0x90e220 + 0x001e9> in <filename unknown>:0 

          at ServiceStack.Host.Handlers.ServiceStackHandlerBase.HandleResponse (System.Object response, System.Func`2 callback, System.Func`2 errorCallback) <0x90dc70 + 0x00221> in <filename unknown>:0 

        InnerException: System.Net.Sockets.SocketException

        The socket has been shut down

          at System.Net.Sockets.Socket.Send (System.Byte[] buffer, Int32 offset, Int32 size, SocketFlags flags) <0x91a400 + 0x00103> in <filename unknown>:0 

          at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x919f40 + 0x000ad> in <filename unknown>:0 

It is a pretty retarted error cause the server relies on a nfs share, and the server that was running one of the nfs shares died. The biggest problem was that i couldnt kill off the PID for the server without hard reset of the freebsd server. 

So yes it was my server, but it shouldnt emby die gracefully if it looses the mounted nfs?
 

[Luke 37090]

It should be handling that gracefully. Can you try a newer version of the mono runtime, perhaps 4.4.2?

[Muad 0]

i will test it after the weekend

[Luke 37090]

Thanks for the update.