#94 minidlna server sometimes not visible

[rohrbage]

I nociced a problem with minidlna. After initial start it works fine on Opensuse 11.4 64bit. Browsing from Sony TV and IPAD works fine.
But after accessing with IPAD in some case the minidlna server is not visible anymore.
The process on the Opensuse is still active, no hint in the minidlna logfile.
Only killing the minidlna process and restarting helps.

Is there a possibilty to switch on a more detailed debug mode to deliver some more details?

[rohrbage]

After running in -debug mode I fond following message:_

2011/09/25 12:26:51] upnphttp.c:1780: info: Serving DetailID: 1135 [/DATA01/MultiMedia/MusicAlphabetical/1/10/10 CC/10 CC - Good Morning Judge.mp3]
[2011/09/25 12:27:47] upnphttp.c:1179: debug: sendfile error :: error no. 32 [Broken pipe]

After that the minidlna server disappeared.

This effect does not happen always, but my test shows that this happens 1 time within 5 tests.
And it has not an affect on this file only , unfortunately the minidlna server disappears.
Reading the code I can see if there is such a problem the reprocessing is stopped.

[Justin Maggard]

That's a generic network connectivity issue. The file transfer will be broken in that case, but it won't affect discovery. Do you see any messages like "minissdp.c:347: debug: Sending SSDP notifies" in the logs after the file transfer gets broken?

[Robin Kluth]

I have an issue where mDLNA is not visible everytime:

1) Start mDLNA - ok.
2) Start my Samsung UE32C6200 - ok
- mdlna share ist not visible...
- After watching ~30 minutes TV, the TV notify me about a new device (mdlna).

Same on my GT-I9100 with AllShare:

1) mdlan is started
2) Starting "AllShare" - no devices found.
- Restarting mdlna solves this, its immediatly visible.

The restart of mdlna helps in both cases, so: After I start a client, I have to restart mdlna to make it visible, or wait ~30 mins.

Is this a bug or only a config-related issue?

mdlan: CVS-version

Thanks ;)

[Justin Maggard]

In almost every case I've seen, it's because there is something on the network (usually the router) that is blocking or filtering out SSDP M-SEARCH discovery packets from the clients, and not letting those packets get to the machine running MiniDLNA. The reason your devices can see MiniDLNA after a restart is because MiniDLNA sends out unsolicited SSDP NOTIFY packets when it starts, according to the spec.

[Robin Kluth]

I think, my router does not block/filter them (Fritz!Box 7112).

It worked earlier with an older build of mDLNA. The server I used mdlan on, is a Zentyal-Server.

Does mdlna logs such ssdp-request/answers?

Thanks for your help!

[Robin Kluth]

DAMN!

jmaggard, you're right :/

SSDP uses 1900UDP - this was closed....

Opened it, restarting mdlna with -d. Started TV, and:

=======
[2011/11/25 20:13:20] minissdp.c:683: info: SSDP M-SEARCH from 172.31.30.104:1025 ST: urn:schemas-ce-org:device:RemoteUIServerDevice:1, MX: 3, MAN: "ssdp:discover"
=======

My C6200 recognizes mdlna immediately after start it :)

Thanks!

[Justin Maggard]

I'm glad you found it. :) I'm going to go ahead and close this bug now.