ANSWERED server is crashing in few minutes

[Pafzedog 2]

Hello,

 

I'm runing emby server 3.5.2 on debian Jessie.

App is crashing quickly with this error message in Systemd status report : 

emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled)
   Active: failed (Result: exit-code) since lun. 2018-07-30 19:43:35 CEST; 16min ago
  Process: 16746 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=5)
 Main PID: 16746 (code=exited, status=5)

juil. 30 19:43:35 Fozzy emby-server[16746]: at System.IO.File.InternalReadAllLines(String path, Encoding encoding)
juil. 30 19:43:35 Fozzy emby-server[16746]: at System.IO.File.ReadAllLines(String path)
juil. 30 19:43:35 Fozzy emby-server[16746]: at System.Net.NetworkInformation.StringParsingHelpers.ParseGatewayAddressesFromRouteFile(String filePath, String interfaceName)
juil. 30 19:43:35 Fozzy emby-server[16746]: at System.Net.NetworkInformation.LinuxIPInterfaceProperties.GetGatewayAddresses()
juil. 30 19:43:35 Fozzy emby-server[16746]: at System.Net.NetworkInformation.LinuxIPInterfaceProperties..ctor(LinuxNetworkInterface lni)
juil. 30 19:43:35 Fozzy emby-server[16746]: at System.Net.NetworkInformation.LinuxNetworkInterface..ctor(String name)
juil. 30 19:43:35 Fozzy emby-server[16746]: at System.Net.NetworkInformation.LinuxNetworkInterface.GetOrCreate(Dictionary`2 interfaces, String name)
juil. 30 19:43:35 Fozzy emby-server[16746]: at System.Net.NetworkInformation.LinuxNetworkInterface.<>c__DisplayClass5_0.<GetLinuxNetworkInterfaces>b__1(String name, IpAddressInfo* ipAddr, UInt32* scopeId)
juil. 30 19:43:35 Fozzy emby-server[16746]: InnerException: System.IO.IOException
juil. 30 19:43:35 Fozzy emby-server[16746]: System.IO.IOException: Permission denied

I notice that it happen since emby 3.5.1, It seems that it did'nt happen with first release 3.5.0 .

thanks for your help.

 

complete server log is here because uploader on this forum failed for me

 

 

[Luke 25095]

This looks permission related. We're trying to query your system for information on your network interfaces and this is causing the crash.

	System.Net.NetworkInformation.NetworkInformationException (13): An error was encountered while querying information from the operating system. ---> System.AggregateException: One or more errors occurred. (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) ---> System.UnauthorizedAccessException: Access to the path '/proc/net/route' is denied. ---> System.IO.IOException: Permission denied

Unfortunately this crash appears to be happening in such a way that I don't think we can just trap it, log it, and continue.

 

Have you configured anything that might be causing this?

[Luke 25095]

https://github.com/dotnet/corefx/issues/22048

[Pafzedog Topic Author 2]

This looks permission related. We're trying to query your system for information on your network interfaces and this is causing the crash.

	System.Net.NetworkInformation.NetworkInformationException (13): An error was encountered while querying information from the operating system. ---> System.AggregateException: One or more errors occurred. (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) (Access to the path '/proc/net/route' is denied.) ---> System.UnauthorizedAccessException: Access to the path '/proc/net/route' is denied. ---> System.IO.IOException: Permission denied

Unfortunately this crash appears to be happening in such a way that I don't think we can just trap it, log it, and continue.

 

Have you configured anything that might be causing this?

 

In fact I was wrong, it happens since 3.5.0, I just checked my command history on my server and I installed new version 3.4.x and I had to reconfigure everything but it worked.

Since I upgraded to 3.5.0 , this crash happens.

Edited July 30, 2018 by Pafzedog

[Luke 25095]

Yea we updated from the .NET Core runtime 2.0 to 2.1 in the 3.5 release so that might be playing a role as well.

[Luke 25095]

What are the contents of your /proc/net/route file?

[Pafzedog Topic Author 2]

here is the content of this file:

Iface	Destination	Gateway 	Flags	RefCnt	Use	Metric	Mask		MTU	Window	IRTT                                                       
eth0	00000000	FE285097	0003	0	0	0	00000000	0	0	0                                                                               
eth0	00285097	00000000	0001	0	0	0	00FFFFFF	0	0	0                                                                               
docker0	000011AC	00000000	0001	0	0	0	0000FFFF	0	0	0

[Luke 25095]

What's your exact debian version?

[Pafzedog Topic Author 2]

 it's : Debian GNU/Linux 8.11 (jessie)

[Pafzedog Topic Author 2]

Hello,

 

any news on this ?

 

Do you think I can hope a fix or a workaround ?

[Luke 25095]

I'm not sure yet. Still researching this. Thanks.

[Pafzedog Topic Author 2]

ok, thanks for answering

[Pafzedog Topic Author 2]

Just for info.

I rollback to previous version 3.4.1.0 and it works nicely.

[Pafzedog Topic Author 2]

Hello,

 

do you find something useful to fix this or it will be a "wontfix" bug ?

 

No offence here, it's just to know if I have to search another way by myself ( docker, OS upgrade, etc...)

 

regards

[Luke 25095]

We are still looking into it. The problem is that the function we are calling is a critical one, so we can't just skip it, however, the exception is also being thrown in a way that we can't catch and handle. The next release will update to the newly released .NET Core runtime 2.1.3 so we can see if that has any impact. Thanks.

[Pafzedog Topic Author 2]

Hello,

 

I upgraded to beta version 3.6 and everything is working fine for now.

[Luke 25095]

Thanks for the feedback !