New Plugins on fresh install (imported ZFS pool) systematically fail installing

[stephenreda]

So, as I described in https://forums.freenas.org/index.php?threads/importing-zfs-created-in-9-2-1-5-on-latest-build.60681/
I imported an existing ZFS pool on a new installation of the latest stable build of Freenas.

I am however puzzled, I can't seem to properly install plugins. (tried sonarr, plexmediaserver). The installatation seems to go fine,
the plugins appear in the 'installed' section of plugins, but never in the tree. Also, I cannot start these plugins. I just get a message on the GUI that something went wrong.

this is the extract of /var/log/messages/

Code:

Jan 15 23:01:15 freenas warden: Building new Jail... Please wait...
Jan 15 23:01:15 freenas warden: zfs clone Main/jails_2/.warden-template-pluginjail@clean Main/jails_2/sonarr_1
Jan 15 23:01:15 freenas warden: Success!
Jan 15 23:01:15 freenas warden: Jail created at /mnt/Main/jails_2/sonarr_1
Jan 15 23:01:16 freenas bridge0: Ethernet address: 02:5c:9b:a4:96:00
Jan 15 23:01:16 freenas kernel: em0: promiscuous mode enabled
Jan 15 23:01:16 freenas kernel: bridge0: link state changed to UP
Jan 15 23:01:16 freenas kernel: bridge0: link state changed to UP
Jan 15 23:01:16 freenas epair0a: Ethernet address: 02:d0:50....
Jan 15 23:01:16 freenas epair0b: Ethernet address: 02:d0:a0...
Jan 15 23:01:16 freenas kernel: epair0a: link state changed to UP
Jan 15 23:01:16 freenas kernel: epair0a: link state changed to UP
Jan 15 23:01:16 freenas kernel: epair0b: link state changed to UP
Jan 15 23:01:16 freenas kernel: epair0b: link state changed to UP
Jan 15 23:01:16 freenas kernel: em0: link state changed to DOWN
Jan 15 23:01:16 freenas kernel: em0: link state changed to DOWN
Jan 15 23:01:16 freenas kernel: epair0a: promiscuous mode enabled
Jan 15 23:01:19 freenas kernel: em0: link state changed to UP
Jan 15 23:01:19 freenas kernel: em0: link state changed to UP
Jan 15 23:01:28 freenas notifier: jexec 1 /usr/pbi/sonarr-amd64/control stop
Jan 15 23:01:28 freenas uwsgi: jexec 1 /usr/pbi/sonarr-amd64/control start 192.168.1.1 12346
Jan 15 23:01:36 freenas uwsgi: [freeadmin.navtree:562] Couldn't retrieve http://192.168.1.100/plugins/sonarr/1/_s/treemenu: timed outx

note that I already had a jail dataset. I couldn't delete it as the drive was 'busy'. I did however remove the existant jails.

any ideas to move forward?

 

[nojohnny101]

Something is wrong with your jail’s networking. Go into each jail’s networking settings (under advanced) and make sure have a proper IP address set, DNS, gateway, etc.

 

[stephenreda]

but I created them from scratch. Shouldn't they take over the system wide settings?

 

[nojohnny101]

Not necessarily.

 

[SweetAndLow]

You need to set a gateway.

 

[stephenreda]

Hi Guys,

So since i set the gateway (192.168.1.254) in the jail settings, the plugins menu now shows the plugin.

However, the plugin still doesn't load. What I also noticed is that the plugin image is not loaded on that view.

Code:

Jan 16 22:33:37 freenas uwsgi: [plugins.utils:88] Couldn't retrieve http://192.168.1.100/plugins/sonarr/1/_s/status: timed out

This indicates that also need to set the gateway address somewhere else?

Jail settings:

 

[nojohnny101]

Did you confirm your "IPv4 netmask" is correct?

I think I already know the answer to this, but your FreeNAS box can ping 8.8.8.8 correct?

 

[stephenreda]

I did get a strange ping reply

Code:

root@freenas:~ # ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=52 time=20.308 ms
64 bytes from 8.8.8.8: icmp_seq=0 ttl=52 time=20.311 ms (DUP!)
64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=19.157 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=19.159 ms (DUP!)
64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=19.308 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, +2 duplicates, 0.0% packet loss
round-trip min/avg/max/stddev = 19.157/19.649/20.311/0.542 ms

I then disables VIMAGE and restarted the jail; everything now works fine. Thanks guys