[Support] binhex - MiniDLNA


130 posts in this topic Last Reply

Recommended Posts

Hello, binhex,

 

I used minidlna on vm before but am quite new to docker.

 

here is my command to start minidlna docker:

 

docker run -d \
    --net="host" \
    --name=minidlna \
    -v /ndisk1/media:/media \
    -v /ndisk1/apps/minidlna:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e SCHEDULE_SCAN_DAYS=06 \
    -e SCHEDULE_SCAN_HOURS=02 \
    -e SCAN_ON_BOOT=no \
    -e UMASK=000 \
    -e PUID=0 \
    -e PGID=0 \
    binhex/arch-minidlna

 

Everything seems fine, but I can't connect to webui or see the server from DLNA client.

 

The docker host is a CentOS 7. 

 

I have a linux/transmission container running on same host w/o any issue.

 

I changed the network to default bridge mode with port as 

 

docker run -d \

 -p 8200:8200 -p 1900:1900 \
 -p 1900:1900/udp \

 

Then I can access the webui but still can't see the server from DLNA client.

 

Any idea?

 

Thanks in advance,

 

ziggy2018

 

===

 

Here is minidlna.log:

 

[2018/02/16 18:46:51] minidlna.c:1048: warn: Starting MiniDLNA version 1.2.1.
[2018/02/16 18:46:51] minidlna.c:1089: warn: HTTP listening on port 8200
[2018/02/16 18:46:51] monitor.c:218: warn: WARNING: Inotify max_user_watches [8192] is low or close to the number of used watches [38] and I do not have permission to increase this limit.  Please do so manually by writing a higher value into /proc/sys/fs/inotify/max_user_watches.

 

supervisord.log:

 

2018-02-16 18:46:49.972923 [info] System information Linux dp_centosm 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 GNU/Linux
2018-02-16 18:46:50.017875 [info] PUID defined as '0'
2018-02-16 18:46:50.075133 [info] PGID defined as '0'
2018-02-16 18:46:50.140959 [info] UMASK defined as '000'
2018-02-16 18:46:50.187453 [info] Permissions already set for volume mappings
2018-02-16 18:46:50.242281 [info] SCAN_ON_BOOT defined as 'no'
2018-02-16 18:46:50.290276 [info] SCHEDULE_SCAN_DAYS defined as '06'
2018-02-16 18:46:50.344725 [info] SCHEDULE_SCAN_HOURS defined as '02'
2018-02-16 18:46:50.391594 [info] Starting Supervisor...
2018-02-16 18:46:50,700 CRIT Set uid to user 0
2018-02-16 18:46:50,700 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing
2018-02-16 18:46:50,702 INFO supervisord started with pid 7
2018-02-16 18:46:51,705 INFO spawned: 'start' with pid 56
2018-02-16 18:46:51,707 INFO spawned: 'crond' with pid 57
2018-02-16 18:46:51,707 INFO reaped unknown pid 8
2018-02-16 18:46:51,717 DEBG 'start' stdout output:
[info] PID file from previous run found, deleting file /home/nobody/.config/minidlna/minidlna.pid...

2018-02-16 18:46:51,717 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-16 18:46:51,737 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140497282205384 for <Subprocess at 140497282206392 with name start in state RUNNING> (stdout)>
2018-02-16 18:46:51,737 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140497282203944 for <Subprocess at 140497282206392 with name start in state RUNNING> (stderr)>
2018-02-16 18:46:51,737 INFO exited: start (exit status 0; expected)
2018-02-16 18:46:51,737 DEBG received SIGCLD indicating a child quit
2018-02-16 18:46:52,739 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 

 

 

 

 

 

Edited by ziggy2018
Link to post
  • 1 month later...
  • Replies 129
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Love this docker, super easy to set up. However, I agree, I should be able to disable rescan on restart. I have like a thousand photos, it takes forever. ------------------ To scan from two differ

Thanks, Raidserver, for the reply. I am away for the holiday and will not be back until Tuesday. I will look at it again then. Thanks

i wouldnt be too concerned with folders within the share having spaces, that should be fine, same deal with files

Posted Images

  • 1 month later...
  • 2 weeks later...

I've been using miniDLNA for some time and only using it for sharing one folder of 6 channel flac music files.  The only issue I have is I have to restart the app just before I go use it or it doesn't show up for the client.  If I then listen long enough, the music will drop and I have to once again restart the app for it to be found again.  I've never time this but I"m guessing it's 30 minutes ish or less.

 

Any thoughts on what would be causing this or how to troubleshoot?

Link to post

I've just accepted the latest MiniDLNA docker update.  Now minidlnad fails to run, producing the following error:

/usr/bin/minidlnad: error while loading shared libraries: libavformat.so.58: cannot open shared object file: No such file or directory

libavformat 57 is present, but not 58.

 

Edited by PeterB
Link to post

ok guys, the image is now fixed up, its not ideal as i had to perform a full system update in order to bring the packages back inline during the build, so its larger than i wanted, but its the simplest approach, if sizes start ballooning in the future then i will have to rethink things.

Link to post
  • 4 weeks later...
On 5/9/2018 at 10:49 PM, TODDLT said:

I've been using miniDLNA for some time and only using it for sharing one folder of 6 channel flac music files.  The only issue I have is I have to restart the app just before I go use it or it doesn't show up for the client.  If I then listen long enough, the music will drop and I have to once again restart the app for it to be found again.  I've never time this but I"m guessing it's 30 minutes ish or less.

 

Any thoughts on what would be causing this or how to troubleshoot?

 

 

Does anyone have any thoughts on why this is happening to me?

 

 

Link to post
  • 1 month later...
  • 1 month later...

I'm having the same issue. miniDLNA is great, but after a certain amount of uptime, as far as I can tell the only way to stop/start it anymore is to reboot unRAID. I was about to post a simple reply to Cekodok to agree with the situation described, but I was in the middle of rebooting at the time, and now that unRAID is back I'm testing to get some logs to post -- and miniDLNA seems fine. I'll post again in a couple of days, with log data...

Link to post
  • 5 months later...

Hi Guys, any thought on why minidlna is not starting? Here is the generate log file.

Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2019-02-11 19:10:58.669054 [info] System information Linux Tower 4.18.20-unRAID #1 SMP Fri Nov 23 11:38:16 PST 2018 x86_64 GNU/Linux
2019-02-11 19:10:58.687740 [info] PUID defined as '99'
2019-02-11 19:10:59.132531 [info] PGID defined as '100'
2019-02-11 19:10:59.939410 [info] UMASK defined as '000'
2019-02-11 19:10:59.959945 [info] Permissions already set for volume mappings
2019-02-11 19:10:59.976632 [info] SCAN_ON_BOOT defined as 'no'
2019-02-11 19:10:59.994948 [info] SCHEDULE_SCAN_DAYS defined as '06'
2019-02-11 19:11:00.016028 [info] SCHEDULE_SCAN_HOURS defined as '02'
2019-02-11 19:11:00.034358 [info] Starting Supervisor...
2019-02-11 19:11:00,262 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing
2019-02-11 19:11:00,262 INFO Set uid to user 0 succeeded
2019-02-11 19:11:00,264 INFO supervisord started with pid 8
2019-02-11 19:11:01,265 INFO spawned: 'start' with pid 63
2019-02-11 19:11:01,266 INFO spawned: 'crond' with pid 64
2019-02-11 19:11:01,266 INFO reaped unknown pid 9
2019-02-11 19:11:01,315 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23220399460008 for <Subprocess at 23220399001256 with name start in state STARTING> (stdout)>
2019-02-11 19:11:01,315 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23220399064704 for <Subprocess at 23220399001256 with name start in state STARTING> (stderr)>
2019-02-11 19:11:01,315 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-11 19:11:01,315 INFO exited: start (exit status 0; expected)
2019-02-11 19:11:01,315 DEBG received SIGCLD indicating a child quit
2019-02-11 19:11:02,316 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

Link to post
  • 1 month later...

I'm getting "Access Denied by server" errors when trying to browse Albums. I can browse genre and artist OK but Albums throws an error - any ideas?


I'm also trying to set the server name using the "friendly_name" variable in the config file but the name still shows as MiniDLNA. Also tried setting as a container variable but again, no luck.

 

Great work by the way. Another vote here for DSD support - hopefully a stable release becomes available soon!

Edited by tw332
Link to post
Yep, I too am still very interested in DSD support
I don't know what the DSD is but there has been no development for miniDLNA for around a year now so this is unlikely to happen.

Sent from my EML-L29 using Tapatalk

Link to post
  • 3 months later...

Is there a way to make minidlna follow symbolic links in the /media directory?

 

I want to point /media to a directory containing only symbolic links to the directories where the photos are located.  Even though I have set "wide_links=yes" in minidlna.conf, a scan does not find my photos.

 

Indeed, 'ls' within the the container console does not list the files contained within the linked directories. 

sh-4.4# ls -l /media
total 92
lrwxrwxrwx 1 nobody users    40 Sep 13 09:34  170708_E-Park -> /net/tower/mnt/user/Photos/170708_E-Park
-rw-rw-r-- 1 nobody users 90551 Apr 10  2018  29497761_918176058363228_5695819176497643520_n.jpg
lrwxrwxrwx 1 nobody users    55 Sep 13 09:33 'Link to 180408_Cling_YWAM_Graduation' -> /net/tower/mnt/user/Photos/180408_Cling_YWAM_Graduation
lrwxrwxrwx 1 nobody users    38 Sep 13 09:33 'Link to 180418_VBCS' -> /net/tower/mnt/user/Photos/180418_VBCS
lrwxrwxrwx 1 nobody users    49 Sep 13 09:33 'Link to 190519_UpsideDownHouse' -> /net/tower/mnt/user/Photos/190519_UpsideDownHouse
lrwxrwxrwx 1 nobody users    50 Sep 13 09:33 'Link to Methodist Youth Surigao' -> '/net/tower/mnt/user/Photos/Methodist Youth Surigao'
sh-4.4# ls /media/170708_E-Park/
ls: cannot access '/media/170708_E-Park/': No such file or directory
sh-4.4# 

 

Edited by PeterB
Link to post
On 9/13/2019 at 11:06 AM, PeterB said:

Is there a way to make minidlna follow symbolic links in the /media directory?

Okay, I've worked out how to do this.

 

I've set the "/media" path to point to the directory containing links.

Then I created a new path pointing to the directory containing all the photos (in sub-directories), with container path "/files".

 

Now I can create links as:

ln -s /files/DirectoryOfPhotos DirectoryOfPhotos

in the /media directory.

 

I can create the links either from the container console or from an ssh session to the unRAID server or from the console on my desktop machine (in each case with the media directory as my current working directory).  I think that the important point is that the link from "/media" points to "/files....".

 

My reason for wanting to do this is that I wanted a single share in which to hold/archive all my photos but didn't want them all to be visible to minidlna.  This way minidlna only offers the photos suitable for viewing on my photoframe.

Link to post
  • 6 months later...
  • 1 month later...

Hi. I just found out that this docker is spinning one of my disks.

It keeps opening files from Disk5 for no reason.
I have not added any new media files in /mnt/user (/media path) and none of the existing files is used by any dlna client...

 

So why minidlna keeps scanning this disk?

 

Thank you...

Edited by mnever33
Link to post
  • 2 months later...

This is the only MiniDLNA container that actually worked for me, nice work sir!

It maps out the minidlna.conf out to my main server folder, so I can edit it and it takes effect on the container.

My slightly tweaked version is this:

docker run -d \
    --net="host" \
    --name=minidlna \
    -v /media/username:/media \
    -v /docker/appdata/minidlna:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e SCAN_ON_BOOT=yes \
    -e UMASK=000 \
    -e PUID=1000 \
    -e PGID=1000 \
    --restart unless-stopped \
    binhex/arch-minidlna:latest

 

To explain, I have a bunch of SSD drives in USB enclosures (JABOD nor RAID).

They are mounted by my Debian 10 to /media/username folder and each disk goes by its label.

So, I have 5 SSD's (each having subdirectories) all located in /media/username folder.

The line "-v /media/vz:/media \" makes MIiniDLNA scrape the library at the disk level, so I have done further mapping in the minidlna.conf file as follows:

root_container=B
media_dir=/media/disk1/KINO-ENG
media_dir=/media/disk1/KINO-RUS
media_dir=/media/disk2/MULT-ENG
media_dir=/media/disk2/MULT-RUS

 

Note the location omits the /username/  from the path - this is due to "-v /media/username:/media \" line.

I use BubbleUPNP (on Android phone) to link the renderer (Kodi) and the library (MiniDLNA) so that when I tap on <Library> my phone screen shows:

KINO-ENG

KINO-RUS

MULT-ENG

MULT-RUS

 

This is due to the "root_container=B" line in the minidlna.conf.

Just my 5c suggestion is to add " --restart unless-stopped \" to the docker run so that MiniDLNA auto-restarts after you boot the server.

Thank you  Binhex, nice work!  I will try out your other containers, next one in line is Minecraft :)

Edited by bpr323
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.