Can't access to minidlna on my TV or my computer

  • Hello,
    I had to reinstall openmediavault on my microHP server a week ago and I can no longer access minidlna on my Samsung TV or Windows 10 PC.
    Before I reinstalled it was working.
    I searched the Internet but I couldn't find a solution.
    Thank you for helping me identify the problem.

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

    Edited 2 times, last by Tamalou ().

  • I had to reinstall openmediavault on my microHP server a week ago and I can no longer access minidlna on my Samsung TV or Windows 10 PC.

    If you had to reinstall OMV then you would have reinstalled minidlna, also you would have recreated the shares etc.

    Raid is not a backup! Would you go skydiving without a parachute?

  • When I do, on my windows computer, a telnet omv.server 8200, it's not responding. Ping is Ok.
    In attachments, you can see captures about my shared folder configuration :

    Images

    • 000409.png

    Files

    • 000408.png

      (14.23 kB, downloaded 99 times, last: )
    • 000410.png

      (25.32 kB, downloaded 112 times, last: )

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • Nobody to help me, please ?

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • Post service minidlna status, mine is:


  • My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • mistery solved, your minidlna is exited ( not active), you must investigate the cause




    Quote from Tamalou

    Loaded: loaded (/etc/init.d/minidlna; generated; vendor preset: enabled)
    Active: active (exited) since Sat 2019-11-30 02:01:26 CET; 1 weeks


    revise logs and try to restart by hand ( minidlna service start or minidlna service restart ).

  • I don't find anything and i re install all an the same problem on the service.
    Is there someone who he can help me ? With a install tutorial or other.

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • With a install tutorial or other.

    There is no tutorial, this is a plugin, the status output shows active (exited) without any error code in this instance simply restarting the service resolves it.
    I have just installed this on my own system, under Diagnostics -> Dashboard -> Services it shows minidlna as enabled and running (2 green dots), service minidlna status displays the same as @raulfg3 I can also stop and start the service from the command line.


    So running service minidlna restart will bring the service back up, should that fail there will be information in the sys log.

    Raid is not a backup! Would you go skydiving without a parachute?

  • I reinstall minidlna and it doesn't work again.
    When I do service minidlna status, I see again the same state : Active (exited)
    If I tape service minidlna stop, The dot in columns Running become red and green when I tape service minidlna start (normal mdrrr)
    In logs menu, in DLNA section, ,I don't see information.

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • I reinstall minidlna and it doesn't work again.

    You don't have to reinstall.


    I just reinstalled this on my own system again, after removing the first instance.


    From the command line I run;
    service minidlna status output;


    clearly shows it's running, then;
    service minidlna stop output;


    clearly shows the service has stopped, checking Diagnostics -> System Logs -> Syslog clearly shows two references systemd[1]: Stopped LSB: minidlna server
    If I restart the service the status displays as running and the Syslog shows systemd[1]: Started LSB: minidlna server


    The only other option is to ensure your OMV is fully up to date from System -> Update Management.


    To prove this works on my Window 10

    Raid is not a backup! Would you go skydiving without a parachute?

  • Thank you for your answer.
    I have no update to do.
    What can I do about it ?

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • What can I do about it ?

    If there are no updates then OMV is up to date as to minidlna I have no idea, restarting the exited service is the answer as there are no error codes in your post 7 to help diagnose the output.


    I have found another thread here regarding minidlna that maybe of some help, also have you simply tried restarting the server.

    Raid is not a backup! Would you go skydiving without a parachute?

  • Yes I reboot the server.


    Is it possible that the problem comes from bad rights on directories? I find it strange that /var/log.minidlna.log is empty

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • sorry, perhaps a new fresh install and config from scratch works in your case .



    Can you do a fresh install on a new boot media?.


    if the new install still fails , you can revert to old boot disk ( your actual boot disk).


    If works, you can continue configuring the entire system.

  • I had already done it : before I used OMV 5 and I did a nex install with OMV 4.
    I'm going to test to install minidlna on my media, without use OMV.

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • I have the same error.
    I'm going to test on a Raspi.

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • It wors on my raspi.
    I'm going to reinstall my OMV.
    Are there any recommendations for installing OMV on an external hard drive?

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

  • I have install again OMV and Extra : it works !!!!!!!
    Thanks to all people to help me.

    My configuration :
    OmV: 4.1.27-1(Arrakis)
    Kernel : Linux 4.19.0-0.bpo.6-amd64
    Server : HP micro Pro-Liant Gen10 (8GoRAM, X3216 1,6Ghz)
    Computers : Windows 10 (19.09) + Ubuntu 19.10

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!