Project

General

Profile

Bug #7078

can't start installed plugins after 9.3 update

Added by Colby Swandale almost 6 years ago. Updated about 3 years ago.

Status:
Closed: Behaves correctly
Priority:
Nice to have
Assignee:
John Hixson
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

after the 9.3 update completed the existing plugins that i have installed cannot be started from from the plugins page. I can start the jail but i would prefer the ability to perform updates to plugins etc.

As stated above i can start the jail successfully both via the GUI and CLI

warden start plexmediaserver_1
Mounting user-supplied file-systems
jail -c path=/mnt/storage/jails/plexmediaserver_1 name=plexmediaserver_1 host.hostname=plexmediaserver_1 allow.raw_sockets=true pers
ist vnet=new
jexec: jail "ifconfig" not found
Setting IPv4 address: 10.0.0.201/24
inet6_enable: -> YES
ip6addrctl_enable: YES -> YES
add net default: gateway 10.0.0.254
jexec 9 route add default fe80::29c:2ff:fea0:4146
Starting jail with: /etc/rc
jexec 9 /usr/pbi/plexmediaserver-amd64/control start 10.0.0.201 12347

History

#1 Updated by Sean Fagan almost 6 years ago

  • Category set to 33
  • Assignee set to John Hixson

It worked for me (but I only have one plugin).

#2 Updated by John Hixson almost 6 years ago

  • Status changed from Unscreened to Screened
  • Target version set to Unspecified

Are you using IPv6 by chance? Can you also do some basic network troubleshooting on your jails?

for each jail in the output of "jls", can you do the following:

jexec ${JAILID} ifconfig -a # where ${JAILID} is the jail ID from "jls"

try and ping the IPv4 address
if using IPv6, try pinging that address as well
jexec ${JAILID} ping ${IPV4_ADDRESS_OF_FREENAS_BOX}

if using IPv6
jexec ${JAILID} ping6 ${IPV6_ADDRESS_OF_FREENAS_BOX}
Edit Watch Copy

#3 Updated by Colby Swandale almost 6 years ago

John Hixson wrote:

Are you using IPv6 by chance? Can you also do some basic network troubleshooting on your jails?

for each jail in the output of "jls", can you do the following:

jexec ${JAILID} ifconfig -a # where ${JAILID} is the jail ID from "jls"

try and ping the IPv4 address
if using IPv6, try pinging that address as well
jexec ${JAILID} ping ${IPV4_ADDRESS_OF_FREENAS_BOX}

if using IPv6
jexec ${JAILID} ping6 ${IPV6_ADDRESS_OF_FREENAS_BOX}
Edit Watch Copy

No, I'm not using IPV6.

[root@storage] ~# jexec 12 ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair8b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:44:14:00:09:0b
        inet 10.0.0.201 netmask 0xffffff00 broadcast 10.0.0.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
[root@storage] ~# ping 10.0.0.201
PING 10.0.0.201 (10.0.0.201): 56 data bytes
64 bytes from 10.0.0.201: icmp_seq=0 ttl=64 time=0.021 ms
64 bytes from 10.0.0.201: icmp_seq=1 ttl=64 time=0.017 ms
64 bytes from 10.0.0.201: icmp_seq=2 ttl=64 time=0.017 ms
64 bytes from 10.0.0.201: icmp_seq=3 ttl=64 time=0.031 ms
^C
--- 10.0.0.201 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.017/0.022/0.031/0.006 ms

#4 Updated by Colby Swandale almost 6 years ago

Well this is certainly curious, The plugins are now appearing as expected. Status information and the ability to update plugins are all working.

I haven't touched anything in the past few days and i am the only person that has access to this machine. So i guess leave it then?

#5 Updated by John Hixson almost 6 years ago

  • Status changed from Screened to Closed: Behaves correctly

Colby Swandale wrote:

Well this is certainly curious, The plugins are now appearing as expected. Status information and the ability to update plugins are all working.

I haven't touched anything in the past few days and i am the only person that has access to this machine. So i guess leave it then?

Well, if everything works as expected, then there is no problem here ;-) If it happens again, you know what to do.

#6 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Target version changed from Unspecified to N/A

Also available in: Atom PDF