MiniDLNA 1.0.24 - 1.7 (18-Feb-2012)

[voiper99]

Worked perfectly, thanks a lot buddy

However, I did encounter another issue. All of my movies are on an 2TB hard drive attached to the Live via USB. Now when I MiniDLNA to look at one of my directories, it worked fine, however, when I got it to look at all of my directories, it froze up. I tried rebooting a couple of times, and each time it happened. I have since stopped the MiniDLNA service and the Live does not freeze any more, so I can only assume that this issue has something to do with MiniDLNA. Could it be that it has too many movies to index/share so it locks up? If I leave it running, will it eventually start working again?

When I say locks up, I mean I cannot SSH to it nor can I get to the web GUI or control it on my TV with my remote, however, pings still do work.

I probably have 200+ files, all of which are rips of my DVD collection (I thought I should mention that in case the issue has something to do with the size of the files being shared).

Any ideas as to what's going on? Should I perhaps put the config file on my attached USB drive instead of /conf?

Thanks!

[RMerlin]

Where is your database stored? /conf should only have the minidlna.conf file. Make sure MINIDLNA_DBPATH (on the configuration interface) points to somewhere on your hard disk.

[voiper99]

Thanks for the quick reply.

Originally it was in /tmp, but then I moved it to /conf and then I moved it to my USB drive, but all of these locations had the same result. I issued the top command and then started the minidlna service and saw CPU utilization go between 80% to 97% due to the minidlna process, then eventually I lose connectivity to the box.

I assume the cause of the issue is that the minidlna process uses the entire CPU which then crashes the box.

Are there any work arounds for this? Perhaps limiting the amount of CPU the minidlna process can use?

Thanks!

[RMerlin]

CPU usage has nothing to do with it. What it could be doing however is crashing on a corrupted file it can't process (MiniDLNA ain't the most sturdy piece of code in that department...). Try splitting your collection of files until you can confirm if a specific file is causing an issue.

You could also monitor free memory using the "free" command over SSH to ensure you're not running out of memory.

And never save anything in /conf beside what told by a dev. That area only contains less than 100 KB, and filling it might cause you to, at best, crash your WDTV, and at worse, scrap ALL your settings and forcing you to reconfigure everything.

[RMerlin]

MiniDLNA 1.6 is now available. One important change with this build is that I no longer include the required ffmpeg libraries. You must also install the separate ffmpeg.app.bin, which will provide those required libraries.

This new version is also based on MiniDLNA 1.0.21, which is the latest official release at this time.

See original post for download links (either from my website or through Addons Manager).

[Angus_NB]

[RMerlin]

[Angus_NB]

[RMerlin]

Click on "Enable MiniDLNA" to have it start at boot time.

[Angus_NB]

I do have Enable MiniDLNA checked.


But I still have to start it under Plugin Daemons after I reboot.