[SOLVED] All LAN devices discover N54L OMV, except Smart (DLNA enabled) TV

    • OMV 4.x
    • Resolved
    • [SOLVED] All LAN devices discover N54L OMV, except Smart (DLNA enabled) TV

      Hi All,

      I’m new to this forum, OMV, and Linux in general.

      User experience:
      • Microsoft and Windows – Advanced
      • Networking, LAN, WLAN, WAN, VPN setups – intermediate to Advanced
      • Linux – beginner (I often use my Ubuntu Live USB to get me out of trouble with windows HDDs etc)
      • OMV - beginner
      Situation:
      • I’m replacing my old RAID 0 Medion Server (Linux based), with an N54L that has been sitting in my cupboard for the last 3years (needs an OS installed).
      Key issue:
      • The same TV discovered WHS 2011 OS straight out of the box (but not OMV OS)
      • I've installed OMV successfully and have RAID10 with file structure discoverable on wireless laptops and various other devices - except my primary TV
      • All my LAN devices discover the new N54L with OMV, except my new Hisense 55n6 Smart (DLNA enabled) TV.
      What I’ve done to try resolve the issue:
      • Installed Plex on OMV, and it worked on the Hisense TV, but don’t want to use plex (I will go back to WHS 2011 before plex – just another account and password)
      • Played with all manner of settings in the router, used a mix of 2.4 and 5Ghz, ACL, DMZ, open ports, etc
      What I’m thinking:
      • Something to do with ports? 8200? 9001? (ports not changeable on Smart TV)
      • Something to do with Upnp? SAMBA? DLNA combability? (my in-depth knowledge of these protocols is limited)
      • Guest accounts in permissions? (Router's Guest account function turned off. with Guest function 'on', TV can't see any devices)


      I want to migrate to OMV but now I am finally stumped! – I don’t really want to go back to WHS 2011 - but this is my last-ditch effort to use OMV.

      Does anyone have suggestions before I go back to WHS 2011?

      I’ve attached a graphic of my system to this post

      Thanks in advance

      Glen
      Images
      • OMV+Harware setup.png

        305.02 kB, 1,223×686, viewed 146 times

      The post was edited 2 times, last by glen_cqu: Added detail to 'key issues' and 'thinking' Updated image of system with WHS 2011 ().

    • bahahah (thanks for sticking the neck out :) yes, miniDLNA plugin installed.

      Specs on my blu-ray player are DLNA and the blu-ray player can see and stream videos from OMV server.
      With this as evidence, I assume the miniDLNA is working fine

      I welcome any suggestion, no matter how beginner level the suggestion is.

      I'm completely stumped!
    • I use a SAMSUNG TV but it got the same problems (not seeing ...) as other devices - mostly Linux systems - I have.

      This is voodoo (somebody likes to explain?):

      I worked the permissions heavily. All shares got a recursive reapply of the rights. I even did it on the commadline via chmoding differently on files and directories.
      I made sure that the DLNA users where in the access groups.

      In the end I think this was just overkill on my side it should work out of the box.

      Try a rescan under DLNA settings. T h i s t a k e s a l o o o n n g t i m e...

      I came to this voodoo conclusion after setting up a new share with just a few pictures and it worked from the beginning.
      Then I watched the rescan of my intended shares via htop. In the web surface it seemed to be finished but the job ran and ran in the background.

      Once it is finished (sorry no estimate for GBytes/min) everything works. Adding additional files seems to be instant.

      So I think the first setup/scan takes a lot of time and you just have to wait until it is finished.
      I share about a 500 GByte via DLNA. Directory structures with small files like fotos seem to get faster offered than structures containing large files like movies.

      I did not fiddle the /etc/minidlna.conf
      The OMV plugin just handles everything fine for me. I just got the info that my shares are set up and found the location of the database: /var/cache/minidlna here.
      I stopped the DLNA server, deleted the database and restarted. This also takes much time but is worth a try.

      The post was edited 1 time, last by DHGE ().

    • Well it was worth a try :)

      But further investigation, you need to edit the minidlna.conf file located in /ect/ so it's not just a case of installing it and it will work, I have found with Linux you have to apply instructions. But I have found something here which should help.

      I don't use Plex I use Emby inside a Docker container, but Emby has a DLNA server function it just needs to be enabled.

      To go down the route of editing the minidlna conf file I would install winscp and notepad ++ for editing in omv/linux....but the minidlna plugin would use much less overhead than plex or emby.

      EDIT: The minidlna plugin does it all for you, install it>>>enable>>>setup shares via the shares tab....found a youtube vid although it's for a Raspberry Pi it explains the plugin. Depending on the size of your libraries will depend on how long the TV takes to scan.

      Good luck :)
      Raid is not a backup! Would you go skydiving without a parachute?

      The post was edited 1 time, last by geaves ().

    • Thank you All for your effort and answer.
      I now feel like I'm not alone with this issue (not just the user, me :) )

      as a beginner to Linux (especially command line); I think this is going to take a while to fix.

      I will try as per DHGE with resetting databases etc, thanks
      I will also try as per Geaves - I've opened the youtubes and about to watch
      Skybird1980, I'm not sure about Docker (only because I don't know how it works - I need to research). I will delve in to take a look. thanks.

      Geaves; from your link, this articulates the problem "it does not act as a DLNA server. In other words, it is not self-discoverable on the client side"

      Thank you all for the direction.

      I will report back

      Any other suggestions gladly actioned.

      Cheers

      Glen
    • for a complete nooby; could someone please help with step-by-step instructions on how to

      notsofastgrasshopper.blogspot.…-between-smarttv-and.html
      "Point the config file (/etc/minidlna.conf) to the NAS drive and bam! it has catalogued all my music in seconds! There is no UI or web access to this utility. It has a log file to tell you what has been done, so the best way to experience it is to see your music appears on the TV."

      Thanks

      Glen
    • glen_cqu wrote:

      Geaves; from your link, this articulates the problem "it does not act as a DLNA server. In other words, it is not self-discoverable on the client side"
      Ok I've just tested this on my own OMV install (I had to stop Emby as there were errors in the minidlna log) I did this to my SMB Music folder only for testing.

      Installed Minidlna via the plugins
      Select DLNA under services
      Click Enable>>>>Save>>>>Apply
      Shares Tab click Add
      From the drop down selected my music share left the content to all>>>>Save>>>>Apply

      I don't have a Smart TV but I do have a number of W10 machines, iPhones and iPads....this is what appears in file explorer under This PC>>>>Network Locations


      So the plugin works, to test further I open Media Player and VLC on my W10 and MiniDLNA was visible and accessible.

      Initially this failed due to Emby running there were a number of errors in the log file, this is the content of the current log


      Source Code

      1. [2018/08/04 08:06:18] minidlna.c:1034: warn: Starting MiniDLNA version 1.1.6.
      2. [2018/08/04 08:06:18] minidlna.c:340: warn: Creating new database at /var/cache/minidlna/files.db
      3. [2018/08/04 08:06:18] minidlna.c:1074: warn: HTTP listening on port 8200
      4. [2018/08/04 08:06:18] scanner.c:726: warn: Scanning /var/lib/minidlna
      5. [2018/08/04 08:06:18] scanner.c:815: warn: Scanning /var/lib/minidlna finished (0 files)!
      6. [2018/08/04 08:06:18] playlist.c:125: warn: Parsing playlists...
      7. [2018/08/04 08:06:18] playlist.c:259: warn: Finished parsing playlists.
      8. [2018/08/04 08:06:18] minidlna.c:154: warn: received signal 15, good-bye
      As you can see the log is now 'clean'.

      So how do you get to the log;

      W10 open a command prompt
      Type in ssh root@<hostname or ip of omv> Enter
      Type in your root omv password>>>Enter
      You should now have a prompt for your omv......root@<hostname or ip>:~#
      Type nano /var/log/minidlna.log>>>Enter
      You should now see the log file in the editor

      Are there any errors particularly 'bind' errors.

      Apologies for the 'suck eggs' but I thought it was the best way to explain.

      If you get that far we can start to look further if there are any errors.

      Now I've got reset my own system :)

      EDIT: Footnote, forgot, once install was complete I got the usual Windows Firewall popup to allow MiniDLNA access to the 'private network'

      EDIT 2: So further searching it seems that any DLNA server will require firewall or security software to be configured to allow to access the network, which is interesting because I never had to enable anything when I set up Emby, but it could have been done in the background.
      Raid is not a backup! Would you go skydiving without a parachute?

      The post was edited 2 times, last by geaves ().

    • Thanks Geaves.
      Yes, on my other devices I can see the 'swirl' logo for OMV.

      I have also installed shellinabox - and your instructions worked a treat...

      Error log here:...I'm not an expert in reading the log, by my network starts at 192.168.1.1 (not 172.17.0.1)

      2018/07/28 23:21:22] minidlna.c:1034: warn: Starting MiniDLNA version 1.1.6.
      [2018/07/28 23:21:22] minidlna.c:340: warn: Creating new database at /var/cache/minidlna/files.db
      [2018/07/28 23:21:22] minidlna.c:1074: warn: HTTP listening on port 8200
      [2018/07/28 23:21:22] scanner.c:726: warn: Scanning /var/lib/minidlna
      [2018/07/28 23:21:22] scanner.c:815: warn: Scanning /var/lib/minidlna finished (0 files)!
      [2018/07/28 23:21:22] playlist.c:125: warn: Parsing playlists...
      [2018/07/28 23:21:22] playlist.c:259: warn: Finished parsing playlists.
      [2018/07/28 23:21:22] minidlna.c:154: warn: received signal 15, good-bye
      [2018/07/29 08:19:47] minissdp.c:797: error: sendto(udp_shutdown=9): Network is unreachable
      [2018/07/29 08:19:47] minissdp.c:797: error: sendto(udp_shutdown=9): Network is unreachable
      [2018/07/29 08:19:47] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:19:47] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:19:47] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:19:47] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:19:47] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:19:47] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:797: error: sendto(udp_shutdown=9): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:797: error: sendto(udp_shutdown=9): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/29 08:21:39] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/31 21:10:42] minissdp.c:797: error: sendto(udp_shutdown=9): Network is unreachable
      [2018/07/31 21:10:42] minissdp.c:797: error: sendto(udp_shutdown=9): Network is unreachable
      [2018/07/31 21:10:42] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
      [2018/07/31 21:10:42] minissdp.c:314: error: sendto(udp_notify=9, 172.17.0.1): Network is unreachable
    • disabling Docker made no difference :(

      my config file.
      of interest; Line 2 is # (hashed) out

      port=8200
      #network_interface=eth0
      friendly_name=OpenMediaVault
      db_dir=/var/cache/minidlna
      log_dir=/var/log
      album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jp$
      inotify=yes
      enable_tivo=no
      strict_dlna=no
      notify_interval=60
      serial=31446138
      model_number=1
      root_container=B
      log_level=general,artwork,database,inotify,scanner,metadata,http,ssdp,tivo=error
      media_dir=/srv/dev-disk-by-label-RAID10/Music
      media_dir=/srv/dev-disk-by-label-RAID10/Video

      **END
    • [SOLVED]

      Thank you all for your help - especially Geaves

      the solution I found is....

      open>Shellinabox
      pico /etc/minidlna.conf
      [change] <notify_interval=60> to <notify_interval=895>

      In searching around ubuntu and miniDLNA - aparently 895 is default.
      my OMV default was 60

      My TV found the server = very happy :)

      Thank you all for your help!

      Glen
    • Thank you DHGE, I'm a little confused now...

      so based on your stockoverflow forum, should I set <inotify=yes> and all will be good?

      Thanks

      Glen

      Edit 1: I tested the notify_interval=895 several times (with each change of the variable, I stopped and (re)started miniDLNA <sudo /etc/init.d/minidlna stop/start>)
      whenever the number was 60 = no TV
      whenever the number was 895 = TV

      The post was edited 1 time, last by glen_cqu ().

    • Source Code

      1. user@hc1:~$ cat /etc/minidlna.conf
      2. port=8200
      3. #network_interface=eth0
      4. friendly_name=hc1 DLNA
      5. db_dir=/var/cache/minidlna
      6. log_dir=/var/log
      7. album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
      8. inotify=yes
      9. enable_tivo=yes
      10. strict_dlna=no
      11. notify_interval=60
      12. serial=31126138
      13. model_number=1
      14. root_container=.
      15. log_level=general,artwork,database,inotify,scanner,metadata,http,ssdp,tivo=error
      16. media_dir=V,/srv/dev-disk-by-label-Seagate4TB201708/syncthing_root/filme-archiv
      17. media_dir=V,/srv/dev-disk-by-label-Seagate4TB201708/syncthing_root/filme
      18. media_dir=P,/srv/dev-disk-by-label-Seagate4TB201708/syncthing_root/fotos
      19. media_dir=A,/srv/dev-disk-by-label-Seagate4TB201708/syncthing_root/Musik
      Display All
      I really doubt that advertising the server less helps the clients to find it.

      inotify helps. This does not work with every operating system.