Server crashed after lots of Exceptions

[tvinhas 14]

I can't really understand why this happened, and would appreciate some feedback.

 

The full log is attached, and you can see that in the end it just shutdowns the server after lots and lots of errors like this:

        *** Error Report ***
        Version: 3.1.1.0
        Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
        Operating system: Unix 4.4.0.57
        64-Bit OS: True
        64-Bit Process: True
        Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:49:26 UTC 2016)
        Processor count: 6
        Program data path: /var/lib/emby-server
        Application directory: /usr/lib/emby-server/bin
        System.InvalidOperationException: No process is associated with this object.
          at System.Diagnostics.Process.EnsureState (System.Diagnostics.Process+State state) [0x0001e] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.EnsureState (System.Diagnostics.Process+State state) [0x00037] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.GetProcessHandle (System.Int32 access, System.Boolean throwIfExited) [0x00089] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.GetProcessHandle (System.Int32 access) [0x00000] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.Kill () [0x00002] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:Kill ()
          at Emby.Common.Implementations.Diagnostics.CommonProcess.Kill () [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0
          at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.StopProcess (MediaBrowser.MediaEncoding.Encoder.MediaEncoder+ProcessWrapper process, System.Int32 waitTimeMs) [0x00051] in <975693c6a0fc47959b5f01c9ce062347>:0
        System.InvalidOperationException
          at System.Diagnostics.Process.EnsureState (System.Diagnostics.Process+State state) [0x0001e] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.EnsureState (System.Diagnostics.Process+State state) [0x00037] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.GetProcessHandle (System.Int32 access, System.Boolean throwIfExited) [0x00089] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.GetProcessHandle (System.Int32 access) [0x00000] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at System.Diagnostics.Process.Kill () [0x00002] in <bd46d4d4f7964dfa9beea098499ab597>:0
          at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:Kill ()
          at Emby.Common.Implementations.Diagnostics.CommonProcess.Kill () [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0
          at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.StopProcess (MediaBrowser.MediaEncoding.Encoder.MediaEncoder+ProcessWrapper process, System.Int32 waitTimeMs) [0x00051] in <975693c6a0fc47959b5f01c9ce062347>:0

2016-12-24 18:48:49.0690 Error MediaEncoder: Error in WaitForExit
2016-12-24 18:48:49.0690 Info MediaEncoder: Killing ffmpeg process
2016-12-24 18:48:49.0690 Error MediaEncoder: Error killing process

[tvinhas 14]

Forgot to attach the log. Here it is.

 

server-63618134400.txt.gz

[Luke 42077]

Hi, the log messages are not harming anything but i will look at them.

 

The server did not crash - something instructed it to restart.  A restart command was sent. I will add more logging to try to find out where it came from. thanks.