Bloodfire 2 Posted October 22, 2018 Share Posted October 22, 2018 The Emby Server keeps crashing - exit status 05. Here are the logs: 2018-10-21 12:28:23.905 Info App: ServerId: c8934029dd354fad8e4a4b4dee173f192018-10-21 12:28:23.965 Info App: Starting entry point MediaBrowser.WebDashboard.ServerEntryPoint2018-10-21 12:28:23.966 Info App: Entry point completed: MediaBrowser.WebDashboard.ServerEntryPoint. Duration: 0.0010982 seconds2018-10-21 12:28:23.966 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint2018-10-21 12:28:24.065 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.0987951 seconds2018-10-21 12:28:24.065 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint2018-10-21 12:28:24.067 Info App: Loading data from /var/lib/emby/data/connect.txt2018-10-21 12:28:24.075 Info App: Loading data from /var/lib/emby/data/wan.dat2018-10-21 12:28:24.173 Error NetworkManager: Error in GetAllNetworkInterfaces *** Error Report *** Version: 3.5.3.0 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-rpm_{version}_x86_64.rpm Operating system: Unix 4.18.13.1 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 4 Program data path: /var/lib/emby Application directory: /opt/emby-server/system System.Net.NetworkInformation.NetworkInformationException (0x80004005): An error was encountered while querying information from the operating system. ---> System.AggregateException: One or more errors occurred. (Could not find a part of the path '/proc/sys/net/ipv4/conf/veth276e140/forwarding'.) ---> System.IO.DirectoryNotFoundException: Could not find a part of the path '/proc/sys/net/ipv4/conf/veth276e140/forwarding'. Any idea how to prevent the server from crashing every few hours? Link to comment Share on other sites More sharing options...
Bloodfire 2 Posted October 22, 2018 Author Share Posted October 22, 2018 The Emby Server keeps crashing - exit status 05. Here are the logs: 2018-10-21 12:28:23.905 Info App: ServerId: c8934029dd354fad8e4a4b4dee173f192018-10-21 12:28:23.965 Info App: Starting entry point MediaBrowser.WebDashboard.ServerEntryPoint2018-10-21 12:28:23.966 Info App: Entry point completed: MediaBrowser.WebDashboard.ServerEntryPoint. Duration: 0.0010982 seconds2018-10-21 12:28:23.966 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint2018-10-21 12:28:24.065 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.0987951 seconds2018-10-21 12:28:24.065 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint2018-10-21 12:28:24.067 Info App: Loading data from /var/lib/emby/data/connect.txt2018-10-21 12:28:24.075 Info App: Loading data from /var/lib/emby/data/wan.dat2018-10-21 12:28:24.173 Error NetworkManager: Error in GetAllNetworkInterfaces *** Error Report *** Version: 3.5.3.0 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-rpm_{version}_x86_64.rpm Operating system: Unix 4.18.13.1 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 4 Program data path: /var/lib/emby Application directory: /opt/emby-server/system System.Net.NetworkInformation.NetworkInformationException (0x80004005): An error was encountered while querying information from the operating system. ---> System.AggregateException: One or more errors occurred. (Could not find a part of the path '/proc/sys/net/ipv4/conf/veth276e140/forwarding'.) ---> System.IO.DirectoryNotFoundException: Could not find a part of the path '/proc/sys/net/ipv4/conf/veth276e140/forwarding'. Any idea how to prevent the server from crashing every few hours? embyserver-log.txt embyserver-unhandled-log.txt Link to comment Share on other sites More sharing options...
Luke 37229 Posted October 22, 2018 Share Posted October 22, 2018 Hi, this is happening in the .net core runtime. We're hoping this will be resolved for the next release of the server. thanks. Link to comment Share on other sites More sharing options...
Bloodfire 2 Posted October 22, 2018 Author Share Posted October 22, 2018 Thanks Luke! Can't wait for the next release then! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now