Plex Plugin (jail) won't start after upgrade

[gth871r]

I've been running a Plex server that was working just fine under 11.3-U5. This morning I upgraded my system to the new 12.0-U1. Everything seems fine except that the jail that was running my Plex server will not start. I try running it from the plugins and jails menu in the webUI and when I click start it just says starting job and then the jail is sitting there with a status of down and there's no error message.

When I try
"service jail start plex" from the command line I get:
"Cannot 'start' jail. Set jail_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'."

When I try with onestart it gives me:
"Starting jails:/etc/rc.d/jail: WARNING: Invalid configuration for plex (no jail.conf, no hostname, or no path). Jail plex was ignored."

All of my other jails work so I'm hesitant to go mucking about in rc.d without knowing what I'm doing. Anyone else have this problem and manage to solve it?

 

[JohnDigital]

Hello,

Those arent the right commands.

From the host command line run:
iocage list
Take note of your plex jails name and what its status is (release version, down, corrupt, up, etc..) Edit: In fact post this data if you could.
iocage start JAILNAME
Take note of any output that halt the jail from starting and let us know what its telling you. Edit: post this too.

 

[gth871r]

Okay not sure where I found that command but what you sent sounds more right. Here's what happened:

[~]# iocage start plex
No default gateway found for ipv6.
* Starting plex
plex devfs_ruleset 6 does not exist! - Not starting jail

In the GUI under jail properties there's a reference to devfs_ruleset being 6. I have no idea what this is. My other jails all have this as 4 so I changed it to that and now the jail starts but it can't ping anything else on the network (and now that I notice neither can any of my other jails). By the way I'm using IPV4 and have no IPV6 settings anywhere in my network. From the little bit of googling around I've done I understand that devfs was broken on FreeNAS but is now fixed on TrueNAS. I'm closer to working but it's not there yet.

 

[JohnDigital]

This is likely a network issue. Post the output of

ifconfig

Then show me a screenshot of your settings in the GUI NETWORK>GLOBAL

 

[gth871r]

here's ifconfig the internet is on igb0 and there's a VM hosting a website hooked up to igb3 the re0 and igb1and2 aren't used.:

Code:

re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
    ether b4:2e:99:3d:90:0f
    media: Ethernet autoselect (none)
    status: no carrier
    nd6 options=1<PERFORMNUD>
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=a520b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6>
    ether 90:e2:ba:c2:91:10
    inet 10.42.42.2 netmask 0xffffff00 broadcast 10.42.42.255
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
    nd6 options=9<PERFORMNUD,IFDISABLED>
igb1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=e507bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
    ether 90:e2:ba:c2:91:11
    media: Ethernet autoselect
    status: no carrier
    nd6 options=9<PERFORMNUD,IFDISABLED>
igb2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: Public
    options=e507bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
    ether 90:e2:ba:c2:91:12
    media: Ethernet autoselect
    status: no carrier
    nd6 options=9<PERFORMNUD,IFDISABLED>
igb3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=a500b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6>
    ether 90:e2:ba:c2:91:13
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
    nd6 options=1<PERFORMNUD>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
    inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
    inet 127.0.0.1 netmask 0xff000000
    groups: lo
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
    groups: pflog
vlan69: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: Cameras
    options=600703<RXCSUM,TXCSUM,TSO4,TSO6,LRO,RXCSUM_IPV6,TXCSUM_IPV6>
    ether 90:e2:ba:c2:91:11
    groups: vlan
    vlan: 69 vlanpcp: 0 parent interface: igb1
    media: Ethernet autoselect
    status: no carrier
    nd6 options=9<PERFORMNUD,IFDISABLED>
bridge69: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: Bridge for Cameras
    ether 02:8a:4a:f9:c4:45
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto stp-rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vlan69 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 8 priority 128 path cost 2000000
    groups: bridge
    nd6 options=9<PERFORMNUD,IFDISABLED>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:8a:4a:f9:c4:00
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto stp-rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet0.3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 15 priority 128 path cost 2000
    member: vnet0.1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 14 priority 128 path cost 2000
    member: vnet0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 11 priority 128 path cost 2000000
    member: igb3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 5 priority 128 path cost 55
    groups: bridge
    nd6 options=1<PERFORMNUD>
vnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=80000<LINKSTATE>
    ether fe:a0:98:4d:b1:1b
    hwaddr 58:9c:fc:10:ff:df
    groups: tap
    media: Ethernet autoselect
    status: active
    nd6 options=1<PERFORMNUD>
    Opened by PID 2217
bridge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:8a:4a:f9:c4:01
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto stp-rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 13 priority 128 path cost 2000000
    member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 2 priority 128 path cost 20000
    groups: bridge
    nd6 options=1<PERFORMNUD>
vnet1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=80000<LINKSTATE>
    ether fe:a0:98:1d:e5:cc
    hwaddr 58:9c:fc:10:51:0e
    groups: tap
    media: Ethernet autoselect
    status: active
    nd6 options=1<PERFORMNUD>
    Opened by PID 2288
vnet0.1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: SMB as nic: epair0b
    options=8<VLAN_MTU>
    ether 00:1b:21:e2:70:70
    hwaddr 02:2e:4d:c6:cb:0a
    groups: epair
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    nd6 options=1<PERFORMNUD>
vnet0.3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: plex as nic: epair0b
    options=8<VLAN_MTU>
    ether 00:1b:21:14:fa:09
    hwaddr 02:15:be:41:ae:0a
    groups: epair
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    nd6 options=1<PERFORMNUD>

 

[JohnDigital]

Can you ping out on the host?
ping google.com
ping 10.42.42.1

If you are able to ping the gateway from the host\ Make sure all of your jails have the correct IP info set, namely gateway and static IP.

 

[gth871r]

From within the jail I cannot ping anything inside or outside of my network. Nor can I ping the jail 10.42.42.20 from anywhere outside the jail.

 

[JohnDigital]

Right but the host is getting out fine? Doublecheck that you have a defaultrouter setting within the main jail settings of 10.42.42.1 for each jail that isnt getting out.

 

[JohnDigital]

I only asked as you are using your GW and 1.1.1.1 for dns, which is likely ok..

 

[gth871r]

Yes. The host can get on the internet and my internal network just fine. In fact everything works just fine if I go into the UI and select 11.3U5 as my boot environment and restart. That's what's weird. Here's the jail's network configuration if that maybe helps.

 

[JohnDigital]

My next suggestion is confirmed. You should upgrade those jails to the current 12.2-RELEASE. Heres a quick outline:

Create a snapshot of your corresponding pool first.. The one that holds your jails and or plugins, name it preupdate or something clever.

Stop all jails..
iocage list
iocage stop JAILNAME

Run this commands tweak for your use case ifapplicable.
iocage fetch 12.2-RELEASE

Then do this for each jail that is running a 11.3 release
iocage list
iocage upgrade JAILNAME -r 12.2-RELEASE

It will take a minute and theres a few questions and such to be answered so keep a close eye out. Dont close the terminal.

Then once its complete, you should be able to do:
iocage start plex

Then see how its going now

 

[JohnDigital]

Then enter the jail and do (if you are getting out). Do this in each jail (you can also use the GUI, same thing).

pkg update && pkg upgrade

I also dont use Berkeley Packet Filter, and never have. Not sure if you need this or not..

 

[gth871r]

I fetched the 12.2-RELEASE just fine but then the upgrade failed with a bunch of errors relating to being unable to reach pkg.FreeBSD.org. I suspect that it's again related to the networking issue in my jail.

Two things, firstly, I thought you could run a jail as an old version even if the host was on the new version shouldn't plex be perfectly content to run as a 11.3u5 jail until I decide I want to upgrade it?

Secondly, I notice that this whole thing started with an error related to devfs rulesets. We haven't done anything to address that. As I understand that has something to do with the way that the system's devices are seen by the jails. Is there a chance that that's the configuration issue that is causing the problem the network interface isn't passing into the jail correctly?

 

[JohnDigital]

I also dont use Berkeley Packet Filter, and never have. Not sure if you need this or not..

Two things, firstly, I thought you could run a jail as an old version even if the host was on the new version shouldn't plex be perfectly content to run as a 11.3u5 jail until I decide I want to upgrade it?

Youll have issues updating it, but im certain it will "run" fine.. This is on you. I wont stand for a mismatch like this on my system, but your standards might be lower.

The devfs ruleset was an error relating to ip6, we arent using it. Ive never messed with anything else to do with dev rulesets, so not sure.

If your host cant reach pkg then something isnt right.. Your absolutely sure you can ping freebsd.org from the host cli?

 

[Jailer]

I fetched the 12.2-RELEASE just fine but then the upgrade failed with a bunch of errors relating to being unable to reach pkg.FreeBSD.org. I suspect that it's again related to the networking issue in my jail.

This might be related to some changes going on at FreeBSD right now. I've received the same error today so you may want to try this again later in the week. You can read more here about it if you're interested.

 

[gth871r]

Yes I can definitely ping to freebsd.org. When I tried to do the upgrade you described it wound up on 12.1-RELEASE instead of 12.2 I have no idea why that would happen. I suspect that if the freebsd.org site is being wonky as Jailer suggests this may be destined to fail until that is sorted.

 

[JohnDigital]

Did you disable berkeley packet filter, apparently its only needed when you use dhcp.. I never used it, not sure if it might be blocking that jail from getting out..

 

[gth871r]

I disabled that. Still no good. It's the strangest thing. I just noticed that even though I've got IPV6 disabled every way that I can see in the jail configuration when I go into a shell in the jail it still reports that my interfaces have ipv6 addresses. Could that be related.

 

[JohnDigital]

Yes id think so. Try this from the host cli:

iocage exec plex sysrc ipv6_activate_all_interfaces="NO"
iocage restart plex

 

[Jailer]

I think you would be better served by spinning up a fresh jail and running a manual install of plex. So many people have had issues with the plugins I don't know why anyone would run them.