Search the Community

I have installed 4.7.13 and 4.7.12 one by one but not able to run emby-server.How can I run it?

I've noticed that recently Emby has started to crash if I'm selecting somewhat rapidly between movies in my library. I'm by no means an Emby expert, but I have software experience so I checked the log file and found the below: 2017-01-23 07:14:06.4887 Error HttpServer: Error processing request *** Error Report *** Version: 3.1.2.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.59 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: 8 Program data path: /var/lib/emby-server Application directory: /usr/lib/emby-server/bin System.IO.IOException: Unable to write data to the transport connection: The socket has been shut down. ---> System.Net.Sockets.SocketException: The socket has been shut down at System.Net.Sockets.Socket.EndSend (System.IAsyncResult result) [0x00033] in <bd46d4d4f7964dfa9beea098499ab597>:0 at System.Net.Sockets.NetworkStream.EndWrite (System.IAsyncResult asyncResult) [0x0005f] in <bd46d4d4f7964dfa9beea098499ab597>:0 --- End of inner exception stack trace --- at Mono.Security.Protocol.Tls.SslStreamBase.EndWrite (System.IAsyncResult asyncResult) [0x00057] in <1d0bb82c94e7435eb09324cf5ef20e36>:0 at Mono.Net.Security.Private.LegacySslStream.EndWrite (System.IAsyncResult asyncResult) [0x00006] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Mono.Net.Security.Private.MonoSslStreamImpl.EndWrite (System.IAsyncResult asyncResult) [0x00006] in <bd46d4d4f7964dfa9beea098499ab597>:0 at System.Net.Security.SslStream.EndWrite (System.IAsyncResult asyncResult) [0x00006] in <bd46d4d4f7964dfa9beea098499ab597>:0 at System.IO.Stream.<BeginEndWriteAsync>m__8 (System.IO.Stream stream, System.IAsyncResult asyncResult) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 at (wrapper delegate-invoke) System.Func`3[System.IO.Stream,System.IAsyncResult,System.Threading.Tasks.VoidTaskResult]:invoke_TResult_T1_T2 (System.IO.Stream,System.IAsyncResult) at System.Threading.Tasks.TaskFactory`1+FromAsyncTrimPromise`1[TResult,TInstance].Complete (TInstance thisRef, System.Func`3[T1,T2,TResult] endMethod, System.IAsyncResult asyncResult, System.Boolean requiresSynchronization) [0x00002] in <8f2c484307284b51944a1a13a14c0266>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <8f2c484307284b51944a1a13a14c0266>:0 Is there anything that this error indicates that I could be doing differently to fix the situation? I've just started noticing this recently, and a quick restart of emby-server seems to fix it. But obviously, that is not desired to have to restart the service every 4 movies. Also, if there's anything else to check, please let me know and I'll post it. I'm running Emby on Ubuntu Server 16.04 FYI - ASUS mobo w/ i7-6700k Edit: From looking at other posts, it looks like mono sometimes affects stuff like this, but it looks like I'm running 4.6.2.7 which is not a version that folks have said causes problems. Checking the mono-project website I see 4.6.2.16 is released though, so my next step will be trying to update that. $ mono --version Mono JIT compiler version 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:49:26 UTC 2016)