Plex Plugin: Storage / Permissions Problem - Can't find my movies

[awensley]

I'm sorry for asking what I'm sure is a really dumb question, but I'm stumped.

I followed the how-to video on setting up Plex Media Server on my FreeNAS 9.2.1.8 64-bit setup. I followed it exactly with these exceptions:

• My pool is named "awensley"
• My media dataset is named "data"
• My media dataset is set to Share type: "Windows" (and thus Windows ACL). It is intended to also be my Samba share.
• The owner of my share is "awensley:1001", and the group is "users:1003".
  
• I did not check "Allow Guest Access" on the "data" Samba share. I only want authenticated users to access it over the network.
• I created sub-datasets for Movies, Music, Photos, TV, and Videos.
  
• Through Windows accessing the Samba share, I set the permissions for "Everyone" on my "data" share to "Full Control." As I understand it, this should set everything to 777 permissions. I set this recursively. When I click "Change Permissions" on "data" after that, it has every permission checked for owner, group, and other.

My problem: Plex cannot see any of my movie files under /media.

I searched the forum before posting, but the closest post I could find to my problem was this one. I tried the solution posted there. I opened a console on the jail and added my "awensley" user and "users" group with the same IDs, then I added "plex" to the "users" group.

The weird thing is, even as root on jail console, I can't see any of my movie files under /media. I see the Movies, Music, Photos, TV, and Videos folders that I created to hold them, but nothing inside of those directories is visible.

Did I mess things up with my sub-datasets? I set all the owners/groups/permissions on them exactly the same as they are on the parent. I created them because I wanted to be able to see usage and manage compression/quotas/snapshots on each separately.

I'm a FreeBSD/FreeNAS newbie, but I've been a Linux admin for 10 years. I didn't think it would be that different, but perhaps I'm operating on false assumptions.

Thank you for any help or advice.

 

[Joshua Parker Ruehlig]

if you can't see the files as root then it shouldn't be a permission issue. the datasets might just not be mounted for some reason.

to confirm, you mounted you 'data' dataset into the jail to /media using FN?

I personally wouldn't make that many datasets for such similar file types as it just adds complication, but it should still work.

 

[awensley]

Thanks for the reply. Yes, "data" is mounted on /media in the jail. Here are screenshots of my zfs layout, and jail storage.

Storage layout

Plex Jail Storage

The BTSync plugin is also installed, but unconfigured. I'm trying to get Plex working first.

 

[Joshua Parker Ruehlig]

maybe nullfs doesn't span multiple filesystem's (what each of those datasets are). in this case youd need to..

1) mount each dataset under 'data' to a corresponding folder in the jail
2) take my advice and just have all those datasets as just folders in 'data' dataset.

 

[awensley]

That makes sense. Trying #1 right now. If that doesn't work, I'll try 2.

 

[awensley]

Ok, apparently, I cannot remove storage from a jail. No matter what I do, I can't remove the link between /mnt/awensley/data/ and /media/, which means I can't remove the sub-directories in order to link them individually. I've tried deleting the plugin, the jail, and even the dataset that holds all the plugin jails. Every time I re-install Plex, it remembers that I had storage for that jail and re-links /mnt/awensley/data/ and /media/. Frustrating.

Is there a way to remove storage from a jail? Maybe from the command line?

 

[Joshua Parker Ruehlig]

from the freenas host
umount /path/to/mountpoint

use the path in the jail so it doesn't umount the zfs dataset, just the nullfs linking. you can use 'mount' to list all mounts active on your system

 

[awensley]

That worked! Plex now sees my movies. Thank you!

But... of course, I have a new problem. It seems my jail's network access is hosed somehow. Now I keep getting this error in Plex's Web UI:

Plex is not reachable.
Make sure your server has an internet connection and any firewalls or other programs are set to allow access.​

I tried stopping the plugin, then the jail, then restarting the jail, then the plugin, and still have the same error.

Here is the relevant console output:

Oct 20 14:37:37 nas kernel: pid 22382 (Plex Media Server), uid 972: exited on signal 11
Oct 20 14:42:45 nas kernel: epair0a: link state changed to DOWN
Oct 20 14:42:45 nas kernel: epair0b: link state changed to DOWN
Oct 20 14:42:45 nas kernel: re0: link state changed to DOWN
Oct 20 14:42:45 nas kernel: bridge0: link state changed to DOWN
Oct 20 14:42:45 nas kernel: re0: promiscuous mode disabled
Oct 20 14:42:48 nas dhclient: New IP Address (re0): 192.168.1.100
Oct 20 14:42:48 nas kernel: re0: link state changed to UP
Oct 20 14:42:48 nas dhclient: New Subnet Mask (re0): 255.255.255.0
Oct 20 14:42:48 nas dhclient: New Broadcast Address (re0): 192.168.1.255
Oct 20 14:42:48 nas dhclient: New Routers (re0): 192.168.1.1
Oct 20 14:43:11 nas notifier: Performing sanity check on nginx configuration:
Oct 20 14:43:11 nas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Oct 20 14:43:11 nas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Oct 20 14:43:12 nas kernel: bridge0: Ethernet address: 02:a9:8f:c1:d3:00
Oct 20 14:43:12 nas kernel: re0: promiscuous mode enabled
Oct 20 14:43:12 nas kernel: bridge0: link state changed to UP
Oct 20 14:43:12 nas kernel: epair0a: Ethernet address: 02:35:e0:00:0c:0a
Oct 20 14:43:12 nas kernel: epair0b: Ethernet address: 02:35:e0:00:0d:0b
Oct 20 14:43:12 nas kernel: epair0a: link state changed to UP
Oct 20 14:43:12 nas kernel: epair0b: link state changed to UP
Oct 20 14:43:12 nas kernel: epair0a: promiscuous mode enabled
Oct 20 14:43:12 nas kernel: re0: link state changed to DOWN
Oct 20 14:43:12 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Oct 20 14:43:16 nas kernel: re0: link state changed to UP
Oct 20 14:43:20 nas dhclient: New IP Address (re0): 192.168.1.100
Oct 20 14:43:20 nas kernel: arp: 192.168.1.100 moved from 02:35:e0:00:0c:0a to 40:16:7e:b2:c2:a6 on epair0b
Oct 20 14:43:20 nas dhclient: New Subnet Mask (re0): 255.255.255.0
Oct 20 14:43:20 nas dhclient: New Broadcast Address (re0): 192.168.1.255
Oct 20 14:43:20 nas dhclient: New Routers (re0): 192.168.1.1
Oct 20 14:43:37 nas kernel: ifa_del_loopback_route: deletion failed
Oct 20 14:43:37 nas kernel: Freed UMA keg (udp_inpcb) was not empty (80 items). Lost 8 pages of memory.
Oct 20 14:43:37 nas kernel: Freed UMA keg (udpcb) was not empty (840 items). Lost 5 pages of memory.
Oct 20 14:43:37 nas kernel: Freed UMA keg (tcpreass) was not empty (420 items). Lost 5 pages of memory.
Oct 20 14:43:37 nas kernel: Freed UMA keg (tcptw) was not empty (2000 items). Lost 40 pages of memory.
Oct 20 14:43:37 nas kernel: Freed UMA keg (tcp_inpcb) was not empty (1840 items). Lost 184 pages of memory.
Oct 20 14:43:37 nas kernel: Freed UMA keg (sackhole) was not empty (404 items). Lost 4 pages of memory.
Oct 20 14:43:37 nas kernel: Freed UMA keg (tcpcb) was not empty (148 items). Lost 37 pages of memory.
Oct 20 14:43:37 nas kernel: hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Oct 20 14:43:37 nas kernel: hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required​

Those memory errors sound scary. This is a brand new box with 8GB of ECC RAM and a 6-core AMD FX CPU.

If I need to contact Plex about these issues, I'll do that, but this seems to be related to FreeNAS's jails.

 

[Joshua Parker Ruehlig]

I think its a jail alias IP issue. not my avenue of expertise cause freenas jails always work on my network =|

 

[awensley]

Ok. I'll do some more investigation and report back here. Thank you for all your help.

 

[awensley]

Looks like this is actually a problem with Plex.tv's servers. I'm able to obtain meta-data for my library, but logging in won't work (previously, I thought meta-data wasn't loading either, it was just really slow). I checked the Plex logs, and it showed that it was an SSLv3 negotiation problem which Plex just disabled in response to the POODLE vulnerability.

They said they fixed it, but I'm thinking they probably broke it again. I can't login to the Plex forum due to them being "down for maintenance." Hopefully I can confirm the issue with them soon. As it is, FreeNAS appears to be working perfectly! Thanks again.

 

[SweetAndLow]

Out of curiosity what are your hardware spec's. I have seen those memory errors before with people running plex. I run plex and have never seen them but some people do. I would like to gather enough information to be able to investigate them more.

 

[awensley]

On this FreeNAS server, my specs are:

Motherboard: ASUS M5A97 LE R2.0
CPU: AMD FX-6300 (6-core, 3.5Ghz)
RAM: Kingston 8GB DDR3 1600 (PC3 12800) ECC Unbuffered KVR16LE11/8KF

I have plans to upgrade the RAM with three more 8GB sticks (32GB total) eventually, but this is where I started.

By the way, everything's working with Plex now. They fixed whatever problems their servers were having, so I'm a happy camper again.