FreeNAS 11.2 Plex Plugin: Installation fails

[shvi]

When I try to install the Plex Plugin on a fresh installation of FreeNAS 11.2 I get the following error:

Code:

[EFAULT] Exception: URLError: occured, destroyed plex.

The following gets logged to /var/log/messages:

Code:

Jan 15 14:22:25 freenas epair0a: Ethernet address: 02:7a:d0:00:04:0a
Jan 15 14:22:25 freenas epair0b: Ethernet address: 02:7a:d0:00:05:0b
Jan 15 14:22:25 freenas kernel: epair0a: link state changed to UP
Jan 15 14:22:25 freenas kernel: epair0a: link state changed to UP
Jan 15 14:22:25 freenas kernel: epair0b: link state changed to UP
Jan 15 14:22:25 freenas kernel: epair0b: link state changed to UP
Jan 15 14:22:25 freenas kernel: epair0a: changing name to 'vnet0:6'
Jan 15 14:22:25 freenas kernel: vnet0:6: promiscuous mode enabled
Jan 15 14:22:25 freenas kernel: re0: link state changed to DOWN
Jan 15 14:22:25 freenas kernel: re0: link state changed to DOWN
Jan 15 14:22:30 freenas kernel: re0: link state changed to UP
Jan 15 14:22:30 freenas kernel: re0: link state changed to UP
Jan 15 14:22:35 freenas dhclient: New IP Address (re0): 192.168.2.221
Jan 15 14:22:35 freenas dhclient: New Subnet Mask (re0): 255.255.255.0
Jan 15 14:22:35 freenas dhclient: New Broadcast Address (re0): 192.168.2.255
Jan 15 14:22:35 freenas dhclient: New Routers (re0): 192.168.2.1
Jan 15 14:23:48 freenas kernel: vnet0:6: link state changed to DOWN
Jan 15 14:23:48 freenas kernel: vnet0:6: link state changed to DOWN
Jan 15 14:23:48 freenas kernel: epair0b: link state changed to DOWN
Jan 15 14:23:48 freenas kernel: epair0b: link state changed to DOWN
Jan 15 14:23:48 freenas kernel: re0: link state changed to DOWN
Jan 15 14:23:48 freenas kernel: re0: link state changed to DOWN
Jan 15 14:23:48 freenas kernel: bridge0: link state changed to DOWN
Jan 15 14:23:48 freenas kernel: bridge0: link state changed to DOWN
Jan 15 14:23:53 freenas kernel: re0: link state changed to UP
Jan 15 14:23:53 freenas kernel: re0: link state changed to UP
Jan 15 14:23:53 freenas kernel: bridge0: link state changed to UP
Jan 15 14:23:53 freenas kernel: bridge0: link state changed to UP
Jan 15 14:23:58 freenas dhclient: New IP Address (re0): 192.168.2.221
Jan 15 14:23:58 freenas dhclient: New Subnet Mask (re0): 255.255.255.0
Jan 15 14:23:58 freenas dhclient: New Broadcast Address (re0): 192.168.2.255
Jan 15 14:23:58 freenas dhclient: New Routers (re0): 192.168.2.1

I locked the IP address to 192.168.2.221 in the DHCP server.

It looks like a network issue, but being new to FreeNAS, I have no idea how to go about debugging this.

 

[SweetAndLow]

In the webui add these options to your nic '-rxcsum -txcsum -lro -tso -vlanhwtso'. I think there might be a bug with how jails disable offloading.

 

[shvi]

@SweetAndLow Thanks for your quick response!

In the webui add these options to your nic '-rxcsum -txcsum -lro -tso -vlanhwtso'.

Doing so, generates the same [EFAULT] Exception: URLError: occured, destroyed plex. error.

But now the log starts with interface epair 0a removed:

Code:

rtsold[90671]: <rtsock_input_ifannounce> interface epair 0a removed
rtsold[90671]: <rtsock_input_ifannounce> interface epair 0b removed
epair0a: Ethernet address: 02:7a:d0:00:04:0a
epair0b: Ethernet address: 02:7a:d0:00:05:0b
kernel: epair0a: link state changed to UP
kernel: epair0a: link state changed to UP
kernel: epair0b: link state changed to UP
kernel: epair0b: link state changed to UP
kernel: epair0a: changing name to 'vnet0:7'
kernel: vnet0:7: promiscuous mode enabled
rtsold[90671]: <rtsock_input_ifannounce> interface vnet0:7 removed
kernel: vnet0:7: link state changed to DOWN
kernel: vnet0:7: link state changed to DOWN
kernel: epair0b: link state changed to DOWN
kernel: epair0b: link state changed to DOWN
kernel: re0: link state changed to DOWN
kernel: re0: link state changed to DOWN
kernel: bridge0: link state changed to DOWN
kernel: bridge0: link state changed to DOWN
kernel: re0: link state changed to UP
kernel: re0: link state changed to UP
kernel: bridge0: link state changed to UP
kernel: bridge0: link state changed to UP
dhclient: New IP Address (re0): 192.168.2.221
dhclient: New Subnet Mask (re0): 255.255.255.0
dhclient: New Broadcast Address (re0): 192.168.2.255
dhclient: New Routers (re0): 192.168.2.1

You wrote:

I think there might be a bug with how jails disable offloading.

I am not entirely sure I understand what you are saying. Nor do I know what the -rxcsum -txcsum -lro -tso -vlanhwtso options do in the NIC config.

Is there anything else I could try?

 

[SweetAndLow]

Those options just disable the offloading feature from when the nic driver is loaded, instead of doing it when the jail is started. You can remove those flags if it didn't make a difference. I just was talking with someone on IRC that had a very similar problem and that fixed their issue. But looks like it doesn't fix yours.

 

[DrKK]

But what does "URLError" mean in this context? I was thinking he had a nameserver problem, but, if he had a nameserver problem, he wouldn't have been able to get the plex plugin in the first place from the repo...

 

[SweetAndLow]

Yeah not sure what URLError means in this context.

@shvi can you create just a normal jails with and without vnet? Maybe just install plex in one of those? The plugin should work but just creating your own is a good workaround.

 

[PeterT22]

I have the same problem, can't install any plugin. Hope somebody will help me and shvi.

 

[tohuuuuu]

Had the same problem. I solved it by using a fixed IP address for installation purposes, changing to DHCP once the Plex plugin was installed correctly. But anyway, i didn't get Plex to run smoothly on a freshly installed 11.2: with Plex Jail configured for DHCP, i didn't manage to access the web admin interface (plex server not found - no, i didn't try to access the fixed IP, i simply hit "Manage" in the plugin menu...). With a fixed IP assigned to the Plex jail, the web admin interface can be accessed without problems, but now none of my DLNA clients were able to find the Plex DLNA server. Another problem arose regarding the DLNA folders: With DHCP enabled and Plex available for DLNA clients, the three "default" folders Videos, Music and Photos were visible on top level, but they were empty (additional info: my media files are stored outside the Plex jail, but they're available to Plex using a mountpoint. Plex is able to access the media data, since the libraries are indexed by plex, content is available through the web interface). So, indexing media files using Plex was useless to me since they aren't available for DLNA clients.

So my currently "final" solution was installing Emby instead of Plex. Installation still requires assigning a fixed IP to the new Plugin jail, but differently to plex, the emby web admin interface was still available after enabling DHCP. Emby seems to be less "powerful" than Plex, but i works at least, while the Plex plugin simply seems to be broken on 11.2.

Regarding the DHCP issue: this seems to affect not only Plex and Emby. I didn't went through the complete list, but i received the same error trying to install syncthing... see also this thread on a similar problem regarding different plugins and the related bug 62739.

 

[blooper98]

Hi, I have the same problem as shvi and PeterT22 on version 11.2, hoping somebody can help

EDIT: My hardware is, currently:
ASRock J3455-ITX motherboard
Intel J3455 cpu
16 GB of RAM
1 hardrive, 4TB capacity

 

[SweetAndLow]

Can you create a jail

 

[blooper98]

Can you create a jail

I am able to create a jail, and after sucsesfully creating one, I decided to try again with your earlier advice of manually installing, following the guide here: https://forums.freenas.org/index.ph...to-install-plex-in-a-freenas-11-0-jail.19412/

I was able to install pkg & install plex within the jail via the command line as root@myjail

Thanks!