Server crashes since 3.1.0.0 (SocketException)

[theirman 0]

Hi,

 

Just updated the media/emby-server port to 3.1.0, and the server keeps throwing an unhandled exception when starting (find the logs attached).

Reverted back to 3.0.8500 in the meantime as that one works fine (server-63617782744 (8500 old success).txt).

 

2016-12-19 21:51:42.8663 Error App: LoaderException: Could not resolve type with token 0100005f
2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies.
2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies.
2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies.
2016-12-19 21:51:42.8696 Error App: LoaderException: Could not resolve type with token 01000128
2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies.

2016-12-19 21:51:44.4754 Error ServerManager: Error starting Http Server
*** Error Report ***
Version: 3.1.0.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.0.0
64-Bit OS: True
64-Bit Process: True
Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 22:44:12 UTC 2016)
Processor count: 12
Program data path: /var/db/emby-server
Application directory: /usr/local/lib/emby-server
System.AggregateException: One or more errors occurred. ---> MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported
 at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 
 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 
  --- End of inner exception stack trace ---
 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 
 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 
  --- End of inner exception stack trace ---
 at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00014] in <8f2c484307284b51944a1a13a14c0266>:0 
 at System.Threading.Tasks.Task`1[TResult].GetResultCore (System.Boolean waitCompletionNotification) [0x00034] in <8f2c484307284b51944a1a13a14c0266>:0 
 at System.Threading.Tasks.Task`1[TResult].get_Result () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0 
 at SocketHttpListener.Net.EndPointManager.AddPrefixInternal (MediaBrowser.Model.Logging.ILogger logger, System.String p, SocketHttpListener.Net.HttpListener listener) [0x0006a] in <5e2146744a844faab36e869c2bc89d0d>:0 
 at SocketHttpListener.Net.EndPointManager.AddListener (MediaBrowser.Model.Logging.ILogger logger, SocketHttpListener.Net.HttpListener listener) [0x00030] in <5e2146744a844faab36e869c2bc89d0d>:0 
---> (Inner Exception #0) MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported
 at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 
 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 
  --- End of inner exception stack trace ---
 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 
 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 <---

Anything I can do to fix this?

 

Is everyone else also experiencing this problem?

 

Thank you

 

server-63617781102.txt

unhandled_abcf3070-649e-4189-a769-b1c2efb9e65e.txt

server-63617782744 (8500 old success).txt

Edited December 19, 2016 by theirman

[Luke 38860]

Does the platform not support ipv6?

[Luke 38860]

Anyway, we can catch the error and resolve this. thanks.

[theirman 0]

It should... It's the latest freenas, and it has support for ipv6.

It's running in a jail, and the jail doesn't have an ipv6 address associated with it, but it should work.

 

Anything I can do to fix it now, or do I wait for the latest release?

Edited December 19, 2016 by theirman

[Luke 38860]

You'll have to wait for the next build. We'll probably have another one out very soon. thanks.

[Muad 0]

i think freeNAS is still running with warden if so just do this

 warden set ipv6 myjail 2001:db8::2/32
i resolved my problems by adding a ipv6 addr too the jail should be easy enough

Edited December 21, 2016 by Muad

[Luke 38860]

Thanks for the info. We're going to have an update out shortly that will also recover from the error in your log, and just run without ipv6. Thanks.

[theirman 0]

i think freeNAS is still running with warden if so just do this

 warden set ipv6 myjail 2001:db8::2/32

i resolved my problems by adding a ipv6 addr too the jail should be easy enough

Thank you. That made it work for me.