16 replies to this topic

[CBers]

I have had Emby server crash on me twice in the last few hours with Unhandled Exceptions.
 

System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at SocketHttpListener.Net.HttpResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count)
at SocketHttpListener.Net.HttpResponseStream.DisposeCore()
at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at SocketHttpListener.Net.HttpConnection.Close(Boolean force)
at SocketHttpListener.Net.HttpConnection.Close()
at SocketHttpListener.WebSocket.closeServerResources()
at SocketHttpListener.WebSocket.closeHandshake(Byte[] frameAsBytes, Int32 millisecondsTimeout, Action release)
at SocketHttpListener.WebSocket.close(PayloadData payload, Boolean send, Boolean wait)
at SocketHttpListener.WebSocket.close(CloseStatusCode code, String reason, Boolean wait)
at SocketHttpListener.WebSocket.processException(Exception exception, String message)
at SocketHttpListener.WebSocket.<>c__DisplayClass70_0.<startReceiving>b__2(Exception ex)
at SocketHttpListener.WebSocketFrame.ReadAsync(Stream stream, Boolean unmask, Action`1 completed, Action`1 error)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ThreadPoolWorkQueue.Dispatch()
System.Net.Sockets.SocketException
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at SocketHttpListener.Net.HttpResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count)
at SocketHttpListener.Net.HttpResponseStream.DisposeCore()
at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at SocketHttpListener.Net.HttpConnection.Close(Boolean force)
at SocketHttpListener.Net.HttpConnection.Close()
at SocketHttpListener.WebSocket.closeServerResources()
at SocketHttpListener.WebSocket.closeHandshake(Byte[] frameAsBytes, Int32 millisecondsTimeout, Action release)
at SocketHttpListener.WebSocket.close(PayloadData payload, Boolean send, Boolean wait)
at SocketHttpListener.WebSocket.close(CloseStatusCode code, String reason, Boolean wait)
at SocketHttpListener.WebSocket.processException(Exception exception, String message)
at SocketHttpListener.WebSocket.<>c__DisplayClass70_0.<startReceiving>b__2(Exception ex)
at SocketHttpListener.WebSocketFrame.ReadAsync(Stream stream, Boolean unmask, Action`1 completed, Action`1 error)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ThreadPoolWorkQueue.Dispatch()

There are no errors in the server logs.

 

 

[Luke]

Thanks for the report. We'll take a look.

[Maximus Naxsus]

What happend?

1. Updated Emby server to 3.4.1.3.
2. After the Emby Server restart, most images did not show and where not clickable. See attached screenshot.
3. I restarted the entire server, this did not help. 
4. A couple of minutes later the Emby server crashed. 
5. Manuel start, Emby Server is still running.

How do you recommend I proceed?

Thank you!

 

 

EDIT: 
​Update: the problem seems limited to the browsers Pale Moon (27.9.1) and Edge (1709/41.16299.402.0, Windows 10 Mobile). Vivaldi (latest non snapshot) and Edge (1803/42.17134.1.0) are NOT affected!

 

EDIT2: Removed info

Attached Files

•  Emby20180513 - no images.gif   229.05KB   3 downloads

Edited by Maximus Naxsus, 04 April 2019 - 07:19 AM.

[Chillout]

Been getting a lot of server crashes since manually upgrading to 3.4.1.3.  The auto update did not work so I had to download the setup.exe file from the website.

 

 

Logs:

Crash log

Server Log

 

 

 

Attached Files

•  SocketException.txt   3.07KB   1 downloads
•  server log.txt   31.85KB   0 downloads

[skidmarks]

 

Title name is a little wrong...  If I hover the mouse over a selection a very small version of the image will show up...

Edited by skidmarks, 13 May 2018 - 05:23 PM.

[skidmarks]

You can delete or ignore this post...  See it was reported under this post already....

  

    v3.4.1.3 Unhandled Exception (twice)

 

But can verify the image issue.

 

[kanipek]

I am seeing this as well.

 

I also had to do a manual update via setup.exe download. Auto update was stuck in a loop.

Attached Files

•  unhandled_63999744-2847-442e-9392-64f5b1efc5b9.txt   3.08KB   1 downloads
•  embyserver-63661832342.txt   1.09MB   1 downloads

[vector991]

In version 3.4.1.3 beta, images everywhere in the Web UI do not show up (or show up incorrectly if hovered on), but only if I use Microsoft Edge browser.  It shows up fine like before using Chrome and Opera (the other 2 browsers I use on the same system).

 

It's something that has changed from 3.4.1.2, because if I revert it works in Edge again.

[Happy2Play]

To me there are two different issues here.  I see the image issue when viewing in Edge but images work fine in Firefox and Chrome.

 

image issue in Microsoft Edge 41.16299.371.0 (win 10 1709) 

 

Edge 42 in 1803 works fine.

 

 

I do not see the unhandled exception.

Edited by Happy2Play, 13 May 2018 - 07:26 PM.

[FordGT90Concept]

Same here.

 

Last Line in log:

2018-05-13 21:58:55.422 Info HttpServer: H

Exception file:

System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host

   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)

   at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count)

   at SocketHttpListener.Net.HttpResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count)

   at SocketHttpListener.Net.HttpResponseStream.DisposeCore()

   at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing)

   at System.IO.Stream.Close()

   at SocketHttpListener.Net.HttpConnection.Close(Boolean force)

   at SocketHttpListener.Net.HttpConnection.Close()

   at SocketHttpListener.WebSocket.closeServerResources()

   at SocketHttpListener.WebSocket.closeHandshake(Byte[] frameAsBytes, Int32 millisecondsTimeout, Action release)

   at SocketHttpListener.WebSocket.close(PayloadData payload, Boolean send, Boolean wait)

   at SocketHttpListener.WebSocket.close(CloseStatusCode code, String reason, Boolean wait)

   at SocketHttpListener.WebSocket.processException(Exception exception, String message)

   at SocketHttpListener.WebSocket.<>c__DisplayClass70_0.<startReceiving>b__2(Exception ex)

   at SocketHttpListener.WebSocketFrame.ReadAsync(Stream stream, Boolean unmask, Action`1 completed, Action`1 error)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

--- End of stack trace from previous location where exception was thrown ---

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

System.Net.Sockets.SocketException

   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)

   at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count)

   at SocketHttpListener.Net.HttpResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count)

   at SocketHttpListener.Net.HttpResponseStream.DisposeCore()

   at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing)

   at System.IO.Stream.Close()

   at SocketHttpListener.Net.HttpConnection.Close(Boolean force)

   at SocketHttpListener.Net.HttpConnection.Close()

   at SocketHttpListener.WebSocket.closeServerResources()

   at SocketHttpListener.WebSocket.closeHandshake(Byte[] frameAsBytes, Int32 millisecondsTimeout, Action release)

   at SocketHttpListener.WebSocket.close(PayloadData payload, Boolean send, Boolean wait)

   at SocketHttpListener.WebSocket.close(CloseStatusCode code, String reason, Boolean wait)

   at SocketHttpListener.WebSocket.processException(Exception exception, String message)

   at SocketHttpListener.WebSocket.<>c__DisplayClass70_0.<startReceiving>b__2(Exception ex)

   at SocketHttpListener.WebSocketFrame.ReadAsync(Stream stream, Boolean unmask, Action`1 completed, Action`1 error)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

--- End of stack trace from previous location where exception was thrown ---

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Attached logs.

Attached Files

•  emby.zip   636.41KB   0 downloads

[Chillout]

No more crashes running 3.4.1.4 beta.  I guess its fixed.. 

[kanipek]

No more crashes running 3.4.1.4 beta.  I guess its fixed.. 

Looks like it, only been a few hours for me so I will keep an eye on it.

[Maximus Naxsus]

Emby can’t update to the latest beta release here.
I’ll try to at log files in a couple of hours

 

[ebr]

 

Emby can’t update to the latest beta release here.
I’ll try to at log files in a couple of hours

 

 

 

Have you tried simply installing it from the website on top of your existing installation?

[Maximus Naxsus]

Have you tried simply installing it from the website on top of your existing installation?

 

Nope. Any intrest in the logs? If not, your suggestion is exactly what I had in mind as my next troubleshoot option.
​

Can you tell me why suddenly my favorite browser doesn't work anymore with Emby? Is this more of a feature or a bug. I can imagine that Emby might started to be more demanding in HTML support? Pale Moon is not very in to that.
​^{Previous 'new feature' destroyed my IP settings and now I HAVE to register for SSL certificate to be able to recover the original setup and usage.}
​

Edited by Maximus Naxsus, 15 May 2018 - 10:37 AM.

[CBers]

 

Emby can’t update to the latest beta release here.

 

You'll need to download the exe from the website and update manually.

 

See here for further information.

[Maximus Naxsus]

Updated succeeded to 3.4.1.4

I made a mistake, tried to revert the mistake, suddenly everything was fixed

1.       I downloaded the Emby Installer from the website, not from Github

2.       Started the installer

3.       Emby Setup opened in PaleMoon (previously not working with Emby)

4.       Killed the server

5.       Renamed /system to /system.new and renamed /system.old to /system

6.       Started Emby server

7.       All seems good now, Palemoon still works