miniDLNA reset connection after few minutes

bogi32b · 26. Januar 2015

Moin,

Habe gerade einen HP N40L mit OpenMediaVault und miniDNLA installiert, muss aber leider feststellen das ich immer nur ein paar minuten eine Mediadatei anschauen kann. Im LOG finde ich zu der Zeit sowas:
I installed miniDLNA on my OMV on my HP N40L and can see and browse directorys and start media files. After some minutes the played file stops and i need to reconnect to the dlna server.
The log show me this:

Jan 25 22:39:01 openmediavault /USR/SBIN/CRON[4932]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))

Can this be the reason?

What can i do to find the reason?

ryecoaaron · 26. Januar 2015

That error doesn't have anything to do with minidlna. Is there anything in the minidlna log?

bogi32b · 26. Januar 2015

I set miniDLNA logging to Debug but see nothing at this time.

I can try again and check all the log´s more detailed.

btw.
checking http://omv-extras.org/simple/index.php?id=plugins-stable show me that stable version is 1.0.5
checking Style #2 show:
##########################
02-packages:

dpkg -l | grep openmediavault
--------------------------
ii openmediavault 1.11 all Open network attached storage solution
ii openmediavault-extplorer 1.0.6 all OpenMediaVault eXtplorer plugin
ii openmediavault-keyring 0.3 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-minidlna 1.0.10 all OpenMediaVault miniDLNA (DLNA server) plugin
ii openmediavault-omvextrasorg 1.9 all OMV-Extras.org Package Repositories for OpenMediaVault
##########################

is here maybe the source of the problem?

bogi32b · 27. Januar 2015

Tried it again yesterday, nothing in miniDNLA log. At exact this time when the stream was interruppted, this is in the Syslog:

Jan 26 20:45:01 openmediavault /USR/SBIN/CRON[28638]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
Jan 26 20:45:01 openmediavault rrdcached[1998]: Received FLUSHALL

ryecoaaron · 27. Januar 2015

I haven't been doing a very good job keeping the versions up to data on the omv-extras page. So, you have the most recent version installed. This isn't a problem with the plugin though. It is a minidlna problem.

If you are willing to test a new version of minidlna (1.1.4), I created a package.

wget http://omv-extras.org/testing/minidlna_1.1.4-omv1_amd64.deb
dpkg -i minidlna_1.1.4-omv1_amd64.deb

Then disable and re-enable minidlna in the plugin (or reboot).

bogi32b · 27. Januar 2015

Ok, tried this version, much more debugging in the LOG:

Code

[2015/01/27 19:51:09] minidlna.c:1265: debug: HTTP connection from 192.168.2.128:59563
[2015/01/27 19:51:09] clients.c:271: debug: Client found in cache. [Generic DLNA 1.5/entry 1]
[2015/01/27 19:51:09] upnphttp.c:880: debug: HTTP REQUEST: POST /ctl/ContentDir HTTP/1.1
HOST: 192.168.2.134:8200
CONTENT-LENGTH: 416
CONTENT-TYPE: text/xml; charset="utf-8"
SOAPACTION: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse"
USER-AGENT: BD-F5100 DLNADOC/1.50


<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body><u:Browse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ObjectID>64$3$1</ObjectID>
<BrowseFlag>BrowseDirectChildren</BrowseFlag>
<Filter>*</Filter>
<StartingIndex>35</StartingIndex>
<RequestedCount>7</RequestedCount>
<SortCriteria/>
</u:Browse>
</s:Body>
</s:Envelope>
...
[2015/01/27 19:54:34] minidlna.c:1265: debug: HTTP connection from 192.168.2.128:59620
[2015/01/27 19:54:34] clients.c:271: debug: Client found in cache. [Generic DLNA 1.5/entry 1]
[2015/01/27 19:54:34] upnphttp.c:880: debug: HTTP REQUEST: SUBSCRIBE /evt/ConnectionMgr HTTP/1.1
HOST: 192.168.2.134:8200
SID: uuid:da39268a-a654-11e4-8b4f-a0b3ccdf0c43
TIMEOUT: Second-300


[2015/01/27 19:54:34] upnphttp.c:728: debug: ProcessHTTPSubscribe /evt/ConnectionMgr
[2015/01/27 19:54:34] upnphttp.c:730: debug: Callback '' Timeout=300
[2015/01/27 19:54:34] upnphttp.c:731: debug: SID 'uuid:da39268a-a654-11e4-8b4f-a0b3ccdf0c43'
[2015/01/27 19:54:34] upnphttp.c:1216: debug: HTTP RESPONSE: HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Connection: close
Content-Length: 0
Server: 3.16-0.bpo.2-amd64 DLNADOC/1.50 UPnP/1.0 MiniDLNA/1.1.4
Timeout: Second-300
SID: uuid:da39268a-a654-11e4-8b4f-a0b3ccdf0c43
Date: Tue, 27 Jan 2015 18:54:34 GMT
EXT:


[2015/01/27 19:54:49] minissdp.c:647: debug: SSDP M-SEARCH from 192.168.2.128:59000 ST: ssdp:all, MX: 3, MAN: "ssdp:discover"
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: uuid:4d696e69-444c-164e-9d41-a0b3ccdf0c43
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: upnp:rootdevice
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:device:MediaServer:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:service:ContentDirectory:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:service:ConnectionManager:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:
[2015/01/27 19:54:49] minissdp.c:647: debug: SSDP M-SEARCH from 192.168.2.128:59000 ST: ssdp:all, MX: 3, MAN: "ssdp:discover"
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: uuid:4d696e69-444c-164e-9d41-a0b3ccdf0c43
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: upnp:rootdevice
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:device:MediaServer:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:service:ContentDirectory:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:service:ConnectionManager:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:
[2015/01/27 19:54:49] minissdp.c:647: debug: SSDP M-SEARCH from 192.168.2.128:59000 ST: ssdp:all, MX: 3, MAN: "ssdp:discover"
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: uuid:4d696e69-444c-164e-9d41-a0b3ccdf0c43
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: upnp:rootdevice
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:device:MediaServer:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:service:ContentDirectory:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:schemas-upnp-org:service:ConnectionManager:
[2015/01/27 19:54:49] minissdp.c:247: debug: Sending M-SEARCH response to 192.168.2.128:59000 ST: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:
[2015/01/27 19:55:29] minidlna.c:1109: debug: Sending SSDP notifies
[2015/01/27 19:56:29] minidlna.c:1109: debug: Sending SSDP notifies
[2015/01/27 19:56:59] upnphttp.c:1272: debug: sendfile error :: error no. 32 [Broken pipe]
[2015/01/27 19:57:29] minidlna.c:1109: debug: Sending SSDP notifies
[2015/01/27 19:58:29] minidlna.c:1109: debug: Sending SSDP notifies
[2015/01/27 19:59:29] minidlna.c:1109: debug: Sending SSDP notifies

Alles anzeigen

This is the line when the video stops:
[2015/01/27 19:56:59] upnphttp.c:1272: debug: sendfile error :: error no. 32 [Broken pipe]

any ideas???

subzero79 · 27. Januar 2015

Not too much to do here, report with that log and the mediainfo for that particular file at MiniDlna.

Try with different encoded files to see if the same log repeats

bogi32b · 27. Januar 2015

Tried restart and another file, stopped again with the same error (broken pipe).

subzero79 · 27. Januar 2015

Also don't forget to mention the client in your report

bogi32b · 27. Januar 2015

How to create this report? The client is a Samsung BD Player.

ryecoaaron · 27. Januar 2015

Here

subzero79 · 27. Januar 2015

Here :

http://sourceforge.net/p/minid…ist/tickets?source=navbar

Provide the logs, the model BD player, and probably the media info of the video files that give you problems

I also use Samsung, the TV dlna player series 5500 is from like 3 years ago, and i've never had any problems. I only use mp4 and mkv files.

bogi32b · 3. Februar 2015

There is no mystery anymore. I tried another client (Kodi on Amazon FireTV) without any problems, so the problem must be the BD Player.

Jetzt mitmachen!