DLNA not showing media on Greyhole shares

[BlackSmith]

I set up my Amahi home file server on a Dell Optiplex GX280 with Ubuntu 12.04 and it is GLORIOUS. Greyhole is running across multiple physical drives and shows five logical shares. Love it.
I have installed miniDLNA and my Panasonic BluRay player can see the server. Frustratingly, the BluRay cannot see any content. Though /etc/minidlna.conf lists:

Code: Select all

media_dir=A,/mnt/samba/music media_dir=V,/mnt/samba/videos media_dir=V,/mnt/samba/films media_dir=P,/mnt/samba/photos

with these permissions on the shares (xyz is my first user):

Code: Select all

drwxrwx--- 1 xyz users 0 Sep 14 14:34 films/ drwxrwx--- 1 xyz users 0 Sep 13 15:23 library/ drwxrwx--- 1 xyz users 0 Sep 10 01:25 music/ drwxrwx--- 1 xyz users 0 Sep 10 17:56 photos/ drwxrwx--- 1 xyz users 0 Sep 10 17:56 videos/

The greyhole shares are mounted locally using the mount_shares_locally script provided in the Amahi wiki at http://wiki.amahi.org/index.php/Mount_Shares_Locally.
Each time I've tried a different solution I've used

Code: Select all

sudo service minidlna force-reload

to restart minidlna and get the following in /var/log/minidlna.log:

Code: Select all

[2012/09/20 21:01:43] minidlna.c:155: warn: received signal 15, good-bye [2012/09/20 21:01:44] minidlna.c:907: warn: Starting MiniDLNA version 1.0.21 [SQLite 3.7.9]. [2012/09/20 21:01:44] minidlna.c:935: warn: Creating new database... [2012/09/20 21:01:44] minidlna.c:1002: warn: HTTP listening on port 8200 [2012/09/20 21:01:45] inotify.c:182: warn: WARNING: Inotify max_user_watches [8192] is low or close to the number of used watches [. [2012/09/20 21:01:45] inotify.c:89: error: inotify_add_watch(/mnt/samba/music) [Permission denied] [2012/09/20 21:01:45] inotify.c:89: error: inotify_add_watch(/mnt/samba/videos) [Permission denied] [2012/09/20 21:01:45] inotify.c:89: error: inotify_add_watch(/mnt/samba/films) [Permission denied] [2012/09/20 21:01:45] inotify.c:89: error: inotify_add_watch(/mnt/samba/photos) [Permission denied]

What am I missing? I appreciate any help anybody can offer.

[bigfoot65]

DLNA should not be set to use /mnt/samba/share. The default /var/hda/files/share works fine.

When accessing files remotely, there is no need to access them via the /mnt/samba/share. That is intended for manipulation of files locally on the HDA via command line or using a file manager. This does not apply to streaming files. Remote clients work through Samba and the share should be accessed using /var/hda/files/share.

I am using DLNA as such with no issues. I could be mistaken, but I believe that is your problem.

[BlackSmith]

Glorious; thanks.

I'll check it out, but I believe that I tried accessing them through the landing zone directly and got the same behavior. My LZ is not in the standard Amahi place (/var/...) but hopefully that isn't an issue. Thanks for the quick response and I'll post the results when I change minidlna.conf to point to the landing zone.

Thanks again.

[BlackSmith]

YES! That works. Minidlna must point to the greyhole landing zones, not the shares created by mount_shares_locally.

Thanks Bigfoot. You solved it.

[ Post made via iPhone ]

[cpg]

I see no indication that he said anything at all about landing zones.

Maybe you can take a look and why using landing zones is a bad idea in this page about the greyhole landing zone.

The data from the landing zone is temporary, so it goes to their final destination at some point. Hence it's called landing zone.

[BlackSmith]

The reason I mention the landing zones is that the location that BigFoot wrote

DLNA should not be set to use /mnt/samba/share. The default /var/hda/files/share works fine.

When accessing files remotely, there is no need to access them via the /mnt/samba/share. That is intended for manipulation of files locally on the HDA via command line or using a file manager. This does not apply to streaming files. Remote clients work through Samba and the share should be accessed using /var/hda/files/share.

Based on the Amahi wiki, (http://wiki.amahi.org/index.php/Greyhole_landing_zone):

All the data you copy to your HDA's shares will first land into your LZ, which is by default located in /var/hda/files/share_name. Those folders are used as a temporary location for new files, which will be moved into the pooled drives as soon as possible by the Greyhole service, which runs in background.

it appears that the location BigFoot referred to is, in fact, the default landing zone for Amahi's implementation of greyhole.

My understanding of greyhole is that while the files move out of the landing zones, they are then linked to by symlinks in their permanent locations. The links live on in the landing zones. Also, when I changed my setup to match BigFoot's, suddenly my DLNA server began showing 75% of the files that I wanted to share. It appears to be an improvement.

At the bottom, I believe that BigFoot was, in fact, referring to the landing zones when he wrote about /var/hda/files/share as that is the default greyhole landing zone in Amahi. Did I misunderstand that?

Thanks for the help.

[cpg]

You have to forget about landing zones and what greyhole does.

Use the location of the shares (in linux). The path of each share is listed in the Setup > Shares area.

[BlackSmith]

That is the same place. My setup currenty points toward the shares on the Amahi setup page. That location happens to be the landing zone as well. When you check "use storage pool," greyhole then makes the share location a landing zone.

[ Post made via iPhone ]