minidlna runs, but not visible in the network and no http page

Discussion in 'Plugins' started by ikke, Apr 22, 2012.

  1. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 22, 2012

    Hi,

    I upgraded to 8.2 Beta3 and installed the corresponding minidlna. After modifying the permissions on db, and switching from https to http on freenas gui, I got the plugin to start.

    I just can't see it in my network by any uPNP device, why? Also, the jail port 8200 doesn't open properly, just has "404 not found".

    I see from minidlna.log that it starts and finishes scanning the media dirs. While I try access it over browser, the log get's this:


    "[2012/04/22 18:03:01] upnphttp.c:929: warn: / not found, responding ERROR 404"

    I have tried to add "/" to the end of media dirs, no difference. Here is the conf:



    media_dir=/mnt/share/Musaa/
    port=8200
    inotify=yes
    enable_tivo=no
    strict_dlna=no
    notify_interval=895
    friendly_name=MyNAS
    media_dir=V,/mnt/share/Leffaa/
    media_dir=V,/mnt/share/Lisaa Leffaa/

    Any ideas?
  2. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 22, 2012

    Looking at the sockets, I see the ports are being listened OK, but for some reason the service is not broadcasted into net (I assume, since it doesn't show up on the list of upnp hosts):


    # netstat -f inet -an
    netstat: kvm not available: /dev/mem: No such file or directory
    Active Internet connections (including servers)
    Proto Recv-Q Send-Q Local Address Foreign Address (state)
    tcp4 0 0 10.10.10.249.8200 *.* LISTEN
    tcp4 0 0 10.10.10.249.51413 *.* LISTEN
    tcp4 0 0 10.10.10.249.9091 *.* LISTEN
    tcp4 0 0 10.10.10.249.12347 *.* LISTEN
    tcp4 0 0 10.10.10.249.12346 *.* LISTEN
    udp4 0 0 10.10.10.249.39638 *.*
    udp4 0 0 10.10.10.249.1900 *.*
    udp4 0 0 *.* *.*
    udp4 0 0 10.10.10.249.51413 *.*
    udp4 0 0 *.* *.*
  3. bpoteet New Member

    Member Since:
    Apr 23, 2012
    Message Count:
    1
    Likes Received:
    0
    Trophy Points:
    0
    bpoteet, Apr 23, 2012

    I can confirm this same behavior on my new install of 8.2b3; the minidlna logs show files being recognized and inserted into the minidlna DB, but nothing ever shows up on the network. I tried my PS3 and my Google TV and I get nothing; another odd thing was the GUI interface would not allow me to change the port to anything other than 8200. Any changes I made would not persist, and manual edits to the config file would be overwritten every time I restarted the service, even if I did not touch the config interface.
  4. paleoN Active Member

    Member Since:
    Apr 22, 2012
    Message Count:
    1,403
    Likes Received:
    15
    Trophy Points:
    38
    paleoN, Apr 23, 2012

    I think I read somewhere the http page was an intended feature that never made it into minidlna.

    It's my understanding that minidlna makes multicast requests to the network about every 15 minutes. I successfully tested and streamed some files using XBMC. As I wasn't going to wait 15 minutes for discovery I restarted the minidlna service and it popped up right away.
  5. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 23, 2012

    I believe the difference is that in your setup it works and for us two it doesn't. I used to run minidlna earlier too (from ports), and I never had to wait for it to appear. I bet clients also broadcast a query that servers answer back to. But it would be interesting to find out what makes yours work. Did you do any manual configs for it? Are you running 32 or 64 bit host? It might make a difference, I remember seeing some ldconfig file that specified 32bit libs path, but not 64. On the other hand it should not work at all without the libs.

    Thanks for any info, I really would like to get this working.

    I need to figure out the command to run it manually with debug switch on.
  6. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 23, 2012

    the command to run it would be:
    /usr/local/sbin/minidlna -d -R -P /usr/local/minidlna.pid -u udlna

    It started scanning my dirs, let's see if gives some debug output...
  7. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 23, 2012

    no errors, it claims to advertice itself in every 15 mins as paleoN said:


    [2012/04/24 06:15:31] minissdp.c:347: debug: Sending SSDP notifies
    [2012/04/24 06:30:27] minissdp.c:347: debug: Sending SSDP notifies
    [2012/04/24 06:45:22] minissdp.c:347: debug: Sending SSDP notifies
  8. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 24, 2012

    it advertices itself, but for some reason no client sees it.

    $ sudo tcpdump -ni eth2 port 1900 and host 10.10.10.249
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes
    10:15:12.752424 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 297
    10:15:12.752455 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 288
    10:15:12.752464 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 340
    10:15:12.752472 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 352
    10:15:12.752481 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 354
    10:15:12.752490 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 368
    10:15:12.952704 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 297
    10:15:12.952723 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 288
    10:15:12.952732 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 340
    10:15:12.952741 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 352
    10:15:12.952749 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 354
    10:15:12.952758 IP 10.10.10.249.45033 > 239.255.255.250.1900: UDP, length 368
  9. mrmojo New Member

    Member Since:
    Apr 23, 2012
    Message Count:
    2
    Likes Received:
    0
    Trophy Points:
    0
    mrmojo, Apr 24, 2012

    I've been having a similar problem. I've managed to use the command above to to get minidlna to scan my media directories. My dlna client can see my server however no media is available. When I click on Music or Video on the client there is no content.

    Any help most appreciated.
  10. paleoN Active Member

    Member Since:
    Apr 22, 2012
    Message Count:
    1,403
    Likes Received:
    15
    Trophy Points:
    38
    paleoN, Apr 25, 2012

    ikke

    I'm running FreeNAS-8.2.0-BETA3-x64 with vanilla Beta-3 jail & minidlna pbi installs. Once I fixed the permissions for minidlna it was up and running. Are you on i386 or x64? You don't mention what clients you are using or what your network configuration is. Though given that minidlna seems running correctly and broadcasting properly you might have better luck over on the minidlna forums.

    mrmojo

    You also don't mention what clients you are using. Also the type of media matters particularly for strict DLNA clients, ie the container & codecs inside them. Here's a good blog post on why the DLNA protocol itself is crap. Try adding some different types of video files to your media directories or try out a different client to see if it's a client issue.
  11. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 25, 2012

    I'm running x86_64. My network configuration is flat, so:
    freenas8.2B3 - ge switch - ge switch or 10/100 wlan - client

    And I've used UPnPlay and Bubble UPnP on android, and on ubuntu I've used XBMC and UPnP Inspector. These all used to see the freenas minidlna while I had set it up on freenas7 and freenas8 RC something using ports.

    The things changed are the freenas itself, plugins, and HW jump from x86 to x86_64.

    Minor enhancement to the issue though. After I dropped the discover interval time to 90 secs, and added serial and model numbers to 666 (which I hadn't previously set), I now got it visible to UPnP inspector. But not to the others.

    It's like it would not answer for client query broadcasts.
  12. paleoN Active Member

    Member Since:
    Apr 22, 2012
    Message Count:
    1,403
    Likes Received:
    15
    Trophy Points:
    38
    paleoN, Apr 25, 2012

    It turns out I have the same problem. If I start XBMC after minidlna has been started and try to connect to minidlna, with the saved media source, it times out. I get "Could not connect to network server" error in XBMC. It starts working after minidlna does its SSDP multicast broadcast.

    It looks like the clients send out their own multicast request for media servers. Read Skywalker's responses in this thread over on the ReadyNAS forums.

    Then there's what protosd mentioned in this [post=26907]post[/post]. Doing a quick search shows there are or were problems with FreeBSD and multicasts into a jail.
  13. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 25, 2012

    I came yesterday into the same conclusion, the I believe the jail doesn't receive multicasts.
  14. borisattva New Member

    Member Since:
    Apr 22, 2012
    Message Count:
    13
    Likes Received:
    0
    Trophy Points:
    1
    borisattva, Apr 26, 2012

    i'm in the same boat as OPand some others, ie pluging installed and seemingly enabled, but not visible and not web accessible. i also get 404 on JailIP:8200
    i browsed through the jail and noticed that /usr/pbi/minidlna-amd64/www is present, but empty. wouldn't that be the location of any web-accessible content?
    could it be that its blank by default and minidlna is not supposed to be web accessible except for the config page via FreeNAS?
  15. William Grzybowski Active Member

    Member Since:
    May 27, 2011
    Message Count:
    1,657
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    Curitiba, Brazil
    William Grzybowski, Apr 27, 2012

    Minidlna does not have self webinterface, :8200 is for DLNA aware clients, not humans
  16. valesan Member

    Member Since:
    Dec 12, 2011
    Message Count:
    222
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Falconara Marittima, Italy
    valesan, Apr 28, 2012

    I have your same problem with 8.2b3 miniDLNA Pugin and ...
    the service is not detected by the DLNA player.
    but I solved simply by lowering the Discovery interval to 30 seconds when I turn the TV DLNA I have to wait up to 30 seconds to see and have access to my DLNA server!
    is a problem to keep Discovery Interval so low?
  17. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 28, 2012

    it is more like a matter of going around the problem instead of fixing it. I can't see other problem than possibly some useless wakeup events from cpu power save states, which is a minor thing if even that. But it reveals a bug in the system, which might hit harder later somewhere else.
  18. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 29, 2012

    FYI, I filed a bug report about the issue. Please add your findings there, if you come up with something helpful for the developers. E.g. if someone would have a development box of freenas available, where you could put tcpdump into system and monitor if the FreeNAS itself sees the multicasts, and to check if the minidlna jail get's them. Or any jail.

    I don't have tcpdump in my system, and don't want to mess around too much with it until I get replacement disks for the two disks that just broke... :( Maybe next week.

    https://support.freenas.org/ticket/1493
  19. ProtoSD Active Member

    Member Since:
    Jul 1, 2011
    Message Count:
    3,359
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Leaving FreeNAS
    ProtoSD, Apr 29, 2012

    Multicast issues in FreeBSD jails is pretty common, not a FreeNAS specific issue. Before the plugin jail was around, certain people were complaining about this with Serviio in my jail tutorial also. Google for "freebsd jail multicast" and you'll see it's been a problem for awhile.
  20. ikke Member

    Member Since:
    Apr 22, 2012
    Message Count:
    30
    Likes Received:
    0
    Trophy Points:
    6
    ikke, Apr 30, 2012

    MiniDLNA should be re-thought. Either the multicast thing needs to be verified being not working at all in FreeBSD, and think of a workaround or re-implementation. Or then find the right tuning to get the multicast to jail. I'll google some night more about the issue in FreeBSD in general.

    Maybe some ip filters rules could do forwarding to jail or some other trick. Or then just bluntly freeing minidlna out of jail.

Share This Page