Plugins "broken" after update freenas

[Joshua Parker Ruehlig]

if i type jls in the freenas shell i get this :

Code:

[root@freenas ~]# jls                                                          
   JID  IP Address      Hostname                      Path                     
     1  192.168.1.204   TS3                           /mnt/volume01/SERVER/TS3 
     2  -               mineos_1                      /mnt/volume01/SERVER/mineo
s_1                                                                            
     3  -               openvpn                       /mnt/volume01/SERVER/openv
pn                                                                             
     4  -               plexmediaserver_1             /mnt/volume01/SERVER/plexm
ediaserver_1                                                                   
     5  -               subsonic_1                    /mnt/volume01/SERVER/subso
nic_1                                                                          
     6  -               transmission_1                /mnt/volume01/SERVER/trans
mission_1                                                                      
     7  -               webserver                     /mnt/volume01/SERVER/webse
rver    

but i can't follow with restarting, i restart the jail ? or do i do the onestart command ?
as i can see my teamspeak is getting an ip but the rest doesn't (tough the subsonic is working)

i meant restarting the jail from the jails tab. I'm guessing your issue is that those jails don't have a primary IP for the freenas webui to communicate with.

 

[Joshua Parker Ruehlig]

well this thread inspired me. maybe we can get away from IPs and use UNIX file sockets instead. though this probably won't be till freenas 10, lol

 

[FunSkilZZ]

i restarted the jail and then tried to turn the plugin on but it diid not work

Code:

May 11 22:06:13 freenas kernel: epair4a: link state changed to DOWN
May 11 22:06:13 freenas kernel: epair4a: link state changed to DOWN
May 11 22:06:13 freenas kernel: epair4b: link state changed to DOWN
May 11 22:06:13 freenas kernel: epair4b: link state changed to DOWN
May 11 22:06:16 freenas kernel: ifa_del_loopback_route: deletion failed
May 11 22:06:16 freenas Freed UMA keg (udp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (tcptw) was not empty (100 items).  Lost 2 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (tcp_inpcb) was not empty (30 items).  Lost 3 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (tcpcb) was not empty (12 items).  Lost 3 pages of memory.
May 11 22:06:16 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
May 11 22:06:16 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
May 11 22:06:17 freenas epair4a: Ethernet address: 02:f3:1e:00:0b:0a
May 11 22:06:17 freenas epair4b: Ethernet address: 02:f3:1e:00:0d:0b
May 11 22:06:17 freenas kernel: epair4a: link state changed to UP
May 11 22:06:17 freenas kernel: epair4a: link state changed to UP
May 11 22:06:17 freenas kernel: epair4b: link state changed to UP
May 11 22:06:17 freenas kernel: epair4b: link state changed to UP
May 11 22:06:17 freenas kernel: epair4a: promiscuous mode enabled
May 11 22:06:17 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b
May 11 22:06:17 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b

well i assigned static ip's to the jails ..

 

[Joshua Parker Ruehlig]

i restarted the jail and then tried to turn the plugin on but it diid not work

Code:

May 11 22:06:13 freenas kernel: epair4a: link state changed to DOWN
May 11 22:06:13 freenas kernel: epair4a: link state changed to DOWN
May 11 22:06:13 freenas kernel: epair4b: link state changed to DOWN
May 11 22:06:13 freenas kernel: epair4b: link state changed to DOWN
May 11 22:06:16 freenas kernel: ifa_del_loopback_route: deletion failed
May 11 22:06:16 freenas Freed UMA keg (udp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (tcptw) was not empty (100 items).  Lost 2 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (tcp_inpcb) was not empty (30 items).  Lost 3 pages of memory.
May 11 22:06:16 freenas Freed UMA keg (tcpcb) was not empty (12 items).  Lost 3 pages of memory.
May 11 22:06:16 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
May 11 22:06:16 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
May 11 22:06:17 freenas epair4a: Ethernet address: 02:f3:1e:00:0b:0a
May 11 22:06:17 freenas epair4b: Ethernet address: 02:f3:1e:00:0d:0b
May 11 22:06:17 freenas kernel: epair4a: link state changed to UP
May 11 22:06:17 freenas kernel: epair4a: link state changed to UP
May 11 22:06:17 freenas kernel: epair4b: link state changed to UP
May 11 22:06:17 freenas kernel: epair4b: link state changed to UP
May 11 22:06:17 freenas kernel: epair4a: promiscuous mode enabled
May 11 22:06:17 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b
May 11 22:06:17 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b

well i assigned static ip's to the jails ..

any change in jls? so you can't get an IP for a plugin jail?

 

[FunSkilZZ]

no no changes, i installed a ne plex server, and when i type the jls command in the freenas root. it just shows the same list as before.
no new ip's

 

[Joshua Parker Ruehlig]

no no changes, i installed a ne plex server, and when i type the jls command in the freenas root. it just shows the same list as before.
no new ip's

Guessing that's the issue then. Since FreeNAS doesn't know the primary IP of the jail, it doesn't know where to contact plugin at.
I don't have a solution at the moment. But, here's what works for me.

• set a default gateway
  
• for my jails configuration, disable DHCP and set an IP range
• anytime I create a plugin jail, disable VIMAGE, set an interface, and restart the jail
• now the plugin works as expected

 

[FunSkilZZ]

well i tried everything from your last post, enterering the default gateway from my router ...
i do get this :

Code:

May 13 18:29:52 freenas kernel: arp: 00:19:66 ..... is using my IP address 192.168.1.201 on epair4b!
May 13 18:29:52 freenas kernel: arp:00:19:66 ..... is using my IP address 192.168.1.201 on epair4b!

 

[Joshua Parker Ruehlig]

well i tried everything from your last post, enterering the default gateway from my router ...
i do get this :

Code:

May 13 18:29:52 freenas kernel: arp: 00:19:66 ..... is using my IP address 192.168.1.201 on epair4b!
May 13 18:29:52 freenas kernel: arp:00:19:66 ..... is using my IP address 192.168.1.201 on epair4b!

Sorry I don't have a solution that works for you. Hopefully an update randomly fixes this for you.

Planning to help make this system much more robust for FreeNAS10.

 

[Apollo]

well i tried everything from your last post, enterering the default gateway from my router ...
i do get this :

Code:

May 13 18:29:52 freenas kernel: arp: 00:19:66 ..... is using my IP address 192.168.1.201 on epair4b!
May 13 18:29:52 freenas kernel: arp:00:19:66 ..... is using my IP address 192.168.1.201 on epair4b!

Did you edit the code you placed? If so, I suspect your firewall or router delivering the IP addresses via DHCP may have the address range conflicting with the IP address you are using for the jails.

 

[FunSkilZZ]

yess i did, but i made sure that the ip range of the server 192.168.1.200 .... was outside of my routers dhcp range so normally all the ip's that have to do with the server are static assigned