PDA

View Full Version : Device disconnected on Samsung TV-46C650 & BD-C6300



ludo15
05-26-2013, 01:04 AM
Hi,

I've been running problem free for more than 6 months with those 2 devices, but since a recent mezzmo v3.xx update (can't remember which specific version) I've been having a connection issue with those devices.
Typically, while watching a video, after 20-30 minutes, the video stops and I get a "device disconnected" on my TV or BDP.
Once I received the message, I've need to restart the TV or BDP and "stop & start media server" to get it running for another 20/30 min, really annoying...

I've enabled loggin and reproduced the issue.
Here's a small portion of a log:


22917 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] > ---------------------------------------------------------------------
222918 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] INFO> Sending bytes from 0, length=0
222919 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] OUT > 20A8 SendTo: (send) socket 5556, length = 2743, bytes sent = 2743
<?xml version="1.0" encoding="utf-8"?>
<root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:dlna="urn:schemas-dlna-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType>
<dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">DMS-1.50</dlna:X_DLNADOC>
<dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">M-DMS-1.50</dlna:X_DLNADOC>
<friendlyName>Mezzmo</friendlyName>
<manufacturer>Conceiva Pty. Ltd.</manufacturer>
<manufacturerURL>http://www.conceiva.com</manufacturerURL>
<modelDescription>Mezzmo UPnP DLNA Media Server</modelDescription>
<modelName>Mezzmo Media Server</modelName>
<modelNumber>3.2.0.0</modelNumber>
<modelURL>http://www.mezzmo.com</modelURL>
<serialNumber>myserial</serialNumber>
<UDN>uuid:7d139645-f624-69c3-e7cf-63cbbcf77553</UDN>
<UPC/>
<iconList>
<icon>
<mimetype>image/png</mimetype>
<width>48</width>
<height>48</height>
<depth>24</depth>
<url>SmallIcon.png</url>
</icon>
<icon>
<mimetype>image/png</mimetype>
<width>120</width>
<height>120</height>
<depth>24</depth>
<url>LargeIcon.png</url>
</icon>
<icon>
<mimetype>image/jpeg</mimetype>
<width>48</width>
<height>48</height>
<depth>24</depth>
<url>SmallIcon.jpg</url>
</icon>
<icon>
<mimetype>image/jpeg</mimetype>
<width>120</width>
<height>120</height>
<depth>24</depth>
<url>LargeIcon.jpg</url>
</icon>
</iconList>
<serviceList>
<service>
<serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType>
<serviceId>urn:upnp-org:serviceId:ConnectionManager</serviceId>
<SCPDURL>ConnectionManager/scpd.xml</SCPDURL>
<controlURL>ConnectionManager/control</controlURL>
<eventSubURL>ConnectionManager/event</eventSubURL>
</service>
<service>
<serviceType>urn:schemas-upnp-org:service:ContentDirectory:1</serviceType>
<serviceId>urn:upnp-org:serviceId:ContentDirectory</serviceId>
<SCPDURL>ContentDirectory/scpd.xml</SCPDURL>
<controlURL>ContentDirectory/control</controlURL>
<eventSubURL>ContentDirectory/event</eventSubURL>
</service>
<service>
<serviceType>urn:microsoft.com:service:X_MS_MediaReceiverRegist rar:1</serviceType>
<serviceId>urn:microsoft.com:serviceId:X_MS_MediaReceiverRegi strar</serviceId>
<SCPDURL>X_MS_MediaReceiverRegistrar/scpd.xml</SCPDURL>
<controlURL>X_MS_MediaReceiverRegistrar/control</controlURL>
<eventSubURL>X_MS_MediaReceiverRegistrar/event</eventSubURL>
</service>
</serviceList>
</device>
</root>
222920 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] > ---------------------------------------------------------------------
222921 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] > RequestAnswered on socket 5556, PersistentConnection = 0, Reserved6 = 1
222922 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] SOCK > 20A8 closing socket 5576 (UnBlockChain - chain 3E6811C)
222923 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] INFO > Send_Raw: RetVal = -2 (867)
222924 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] INFO > StreamBody: RetVal = -2 (1286)
222925 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] ERROR> StreamDescriptionDocument (4921)
222926 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] INFO > 20A8 fd_counts: readset = 3, writeset = 0, errorset = 3, tv_sec = 0, tv_usec = 0, slct = -1, v = 0
222927 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] INFO > select returned 1
222928 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] SOCK > select triggered readset socket 5556
222929 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] IN > 20A8 recvfrom socket 5556 (0.0.0.0) bytes received = 0

222930 - May 25 10:24:40.625 [ThreadID:20a8] - [20A8] > ---------------------------------------------------------------------
222931 - May 25 10:24:40.640 [ThreadID:20a8] - [20A8] IN > 20A8 recvfrom socket 5556 (0.0.0.0) device gracefully closed this socket
222932 - May 25 10:24:40.640 [ThreadID:20a8] - [20A8] SOCK > 20A8 closing socket 5556 (ProcessAsyncSocket)
222933 - May 25 10:24:40.640 [ThreadID:20a8] - [20A8] INFO > 20A8 fd_counts: readset = 2, writeset = 0, errorset = 3, tv_sec = 430, tv_usec = 708000, slct = 0, v = 430708

Paul
05-27-2013, 07:57 AM
We'll need all the logs to determine the reason for the disconnection. Please zip them all up and email them to us at support [at] conceiva [dot] com.

ludo15
05-27-2013, 11:47 AM
Of course, already sent. Thanks for your help!

Terrence
10-09-2013, 10:06 AM
Sorry to reopen a closed issue, can you tell me if this has been resolved and what was the solution as I am having a similar problem

Paul
10-09-2013, 10:43 AM
Typically the problem is related to router settings. Turn off UPnP in your router and reboot it. Try streaming again.

If no better, then it's best we see a set of logs. Turn on logging in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and restart your Mezzmo server. Reproduce the problem and then stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

Terrence
10-09-2013, 12:51 PM
Logs had already been sent, can you advise if you have received them ?

Paul
10-09-2013, 01:39 PM
Got your logs. We'll analyze them and report back via email.