dex0 0 Posted August 13, 2020 Share Posted August 13, 2020 Hi guys, When waking up my TV (Pansonic Viera TX-55CX700W) from standby, Emby crash with the following error: Emby 4.4.3.0 on Synology. 2020-08-13 23:02:48.496 Debug Dlna: Attempting to create PlayToController from location http://192.168.42.25:55000/dmr/ddd.xml 2020-08-13 23:02:48.497 Debug Dlna: Logging session activity from location http://192.168.42.25:55000/dmr/ddd.xml 2020-08-13 23:02:48.566 Debug HttpClient: HttpClientManager GET: http://192.168.42.25:55000/dmr/ddd.xml 2020-08-13 23:02:48.664 Error HttpClient: Error UnknownError getting response from *** Error Report *** Version: 4.4.3.0 Command line: /var/packages/EmbyServer/target/server/EmbyServer.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121 Operating system: Unix 3.2.40.0 64-Bit OS: False 64-Bit Process: False User Interactive: False Mono: 6.8.0.105 (tarball Sun Mar 29 11:47:24 UTC 2020) Runtime: file:///volume1/@appstore/EmbyServer/3rdparty/mono/6.8.0.105/lib/mono/4.5/mscorlib.dll System.Environment.Version: 4.0.30319.42000 Processor count: 2 Program data path: /var/packages/EmbyServer/target/var Application directory: /volume1/@appstore/EmbyServer/releases/4.4.3.0 System.Net.WebException: System.Net.WebException: Unable to read data from the transport connection: Connection reset by peer. ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. ---> System.Net.Sockets.SocketException: Connection reset by peer --- End of inner exception stack trace --- at System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.ThrowException (System.Net.Sockets.SocketError error) [0x00007] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.GetResult (System.Int16 token) [0x00022] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Threading.Tasks.ValueTask`1+ValueTaskSourceAsTask+<>c[TResult].<.cctor>b__4_0 (System.Object state) [0x00030] in <9d3f0d4bd0fb4c1e8b6c2ac1ba1303ac>:0 --- End of stack trace from previous location where exception was thrown --- at System.Net.WebResponseStream.InitReadAsync (System.Threading.CancellationToken cancellationToken) [0x000db] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebOperation.Run () [0x001d9] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.HttpWebRequest.MyGetResponseAsync (System.Threading.CancellationToken cancellationToken) [0x0027f] in <b373cc92cfb94ef6a19b4f1140645494>:0 --- End of inner exception stack trace --- at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <9d3f0d4bd0fb4c1e8b6c2ac1ba1303ac>:0 Source: System TargetSite: System.Net.WebResponse EndGetResponse(System.IAsyncResult) InnerException: System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. Source: mscorlib TargetSite: Void Throw() at System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.ThrowException (System.Net.Sockets.SocketError error) [0x00007] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.GetResult (System.Int16 token) [0x00022] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Threading.Tasks.ValueTask`1+ValueTaskSourceAsTask+<>c[TResult].<.cctor>b__4_0 (System.Object state) [0x00030] in <9d3f0d4bd0fb4c1e8b6c2ac1ba1303ac>:0 --- End of stack trace from previous location where exception was thrown --- at System.Net.WebResponseStream.InitReadAsync (System.Threading.CancellationToken cancellationToken) [0x000db] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebOperation.Run () [0x001d9] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.HttpWebRequest.MyGetResponseAsync (System.Threading.CancellationToken cancellationToken) [0x0027f] in <b373cc92cfb94ef6a19b4f1140645494>:0 InnerException: System.Net.Sockets.SocketException: Connection reset by peer Source: TargetSite: Note, this does not happen when restarting Emby with my TV on, the DNLA works correctly (PLAY ON is ok) Maybe the TV is really not yet ready when it sends the SSDP and Emby discover it, is there a way to let Emby wait a few seconds before retrying ? Thanks for help embyserver.txt Link to comment Share on other sites More sharing options...
Luke 36884 Posted August 14, 2020 Share Posted August 14, 2020 Hi, what do you mean by crash? Link to comment Share on other sites More sharing options...
dex0 0 Posted August 14, 2020 Author Share Posted August 14, 2020 Hi, Emby itself is still OK but the DNLA extension is not - no devices shown in PLAY ON (ex. my 2 android phones are not shown anymore). It's like the exception break / crash the DNLA device discovery. Link to comment Share on other sites More sharing options...
Luke 36884 Posted August 14, 2020 Share Posted August 14, 2020 What cpu architecture is your nas ? Link to comment Share on other sites More sharing options...
dex0 0 Posted August 14, 2020 Author Share Posted August 14, 2020 Hi, it's an ARM - Marvell ArmadaXP (Synology DS214+) Link to comment Share on other sites More sharing options...
Luke 36884 Posted August 22, 2020 Share Posted August 22, 2020 Ok, please follow along with this: The new package will likely resolve the issue although it's not yet compatible with armv5. We are working on resolving this. If you'd like to help us, please see this posting here: Thanks ! 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