Jump to content

What this error mean ?


Recommended Posts

Posted (edited)
Emby spams very often this error msg

 


2017-11-11 13:48:29.952 Error Dlna: Error sending socket message from 0.0.0.0 to 239.255.255.250:1900

*** Error Report ***

Version: 3.2.36.0

Command line: C:\Users\Dani\AppData\Roaming\Emby-Server\System\EmbyServer.dll C:\Users\Dani\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

Operating system: Microsoft Windows NT 6.2.9200.0

64-Bit OS: True

64-Bit Process: True

User Interactive: True

Processor count: 4

Program data path: C:\Users\Dani\AppData\Roaming\Emby-Server

Application directory: C:\Users\Dani\AppData\Roaming\Emby-Server\System

System.Net.Sockets.SocketException (0x80004005): Ein Socketvorgang bezog sich auf ein nicht verfügbares Netzwerk

   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)

   at System.Net.Sockets.Socket.EndSendTo(IAsyncResult asyncResult)

   at Emby.Server.Implementations.Net.UdpSocket.<>c__DisplayClass22_0.<SendToAsync>b__0(IAsyncResult callbackResult)

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

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Rssdp.Infrastructure.SsdpCommunicationsServer.<SendFromSocket>d__24.MoveNext()

System.Net.Sockets.SocketException

   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)

   at System.Net.Sockets.Socket.EndSendTo(IAsyncResult asyncResult)

   at Emby.Server.Implementations.Net.UdpSocket.<>c__DisplayClass22_0.<SendToAsync>b__0(IAsyncResult callbackResult)

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

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Rssdp.Infrastructure.SsdpCommunicationsServer.<SendFromSocket>d__24.MoveNext()

 


2017-11-11 13:48:30.060 Error Dlna: Error sending socket message from 0.0.0.0 to 239.255.255.250:1900

*** Error Report ***

Version: 3.2.36.0

Command line: C:\Users\Dani\AppData\Roaming\Emby-Server\System\EmbyServer.dll C:\Users\Dani\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

Operating system: Microsoft Windows NT 6.2.9200.0

64-Bit OS: True

64-Bit Process: True

User Interactive: True

Processor count: 4

Program data path: C:\Users\Dani\AppData\Roaming\Emby-Server

Application directory: C:\Users\Dani\AppData\Roaming\Emby-Server\System

System.Net.Sockets.SocketException (0x80004005): Ein Socketvorgang bezog sich auf ein nicht verfügbares Netzwerk

   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)

   at System.Net.Sockets.Socket.EndSendTo(IAsyncResult asyncResult)

   at Emby.Server.Implementations.Net.UdpSocket.<>c__DisplayClass22_0.<SendToAsync>b__0(IAsyncResult callbackResult)

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

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Rssdp.Infrastructure.SsdpCommunicationsServer.<SendFromSocket>d__24.MoveNext()

System.Net.Sockets.SocketException

   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)

   at System.Net.Sockets.Socket.EndSendTo(IAsyncResult asyncResult)

   at Emby.Server.Implementations.Net.UdpSocket.<>c__DisplayClass22_0.<SendToAsync>b__0(IAsyncResult callbackResult)

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

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Rssdp.Infrastructure.SsdpCommunicationsServer.<SendFromSocket>d__24.MoveNext()

Edited by Dani_
Posted

Nothing to worry about. Looks like an error trying to communicate with a dlna device.

Posted

Why not obfuscate this error message a bit so that it looks a bit less concerning to users? When I open my logs and see lots of these socket connection errors, I'm always worried that there's an unresolved issue that could be affecting the performance of my server.

Posted

I suppose but that can also make it difficult to troubleshoot when there actually is a problem.

Posted

I thought you meant that specific error message was not an error at all. How do we differentiate that from a real problem or not? I don't really understand.

 

This user has a problem, posts the error. You say it's not a problem, but that we shouldn't necessarily obfuscate it since it could actually be a problem? How does this work? How do we know if it is or isn't a problem?

Posted

I thought you meant that specific error message was not an error at all. How do we differentiate that from a real problem or not? I don't really understand.

 

This user has a problem, posts the error. You say it's not a problem, but that we shouldn't necessarily obfuscate it since it could actually be a problem? How does this work? How do we know if it is or isn't a problem?

 

I didn't see this user say they had a problem - just a question about the message in the log and Luke answered it.

 

In some other circumstance, there could be some sort of problem experienced by a user where this type of information would be useful.

Posted

We'll try to improve the logging for a future update to make it more clear, thanks.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...