Plugins Not Listed or Loading

[SteffanCline]

When I first set up FreeNAS I installed the s3cmd and owncloud plugins. I clicked on one to configure it on the side panel and both then disappeared from the list. I have deleted and reinstalled but can't get them back into the list where I can modify settings etc.

Is there something I may be missing or need to change in the filesystem?

 

[SweetAndLow]

Can you go to the plugin tab? What version of freenas and what is your hardware? Any logs in /var/log/messages?

 

[SteffanCline]

I can navigate to the plugin tab to delete or add plugins.

I am using a Dell R710 with FreeNAS 9.3.1

I didn't see anything in the logs but will look again.

 

[SteffanCline]

This seems to be the extent of the log from when I just now installed the 2 plugins.

Feb 13 13:05:29 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.1
Feb 13 13:05:43 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.1
Feb 13 13:06:26 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.1
Feb 13 13:06:29 nas warden: Building new Jail... Please wait...
Feb 13 13:06:29 nas warden: zfs clone POOL1/jails/.warden-template-pluginjail@clean POOL1/jails/owncloud_1
Feb 13 13:06:30 nas warden: Success!
Feb 13 13:06:30 nas warden: Jail created at /mnt/POOL1/jails/owncloud_1
Feb 13 13:06:30 nas bridge0: Ethernet address: 02:9d:b1:88:b2:00
Feb 13 13:06:30 nas kernel: bce0: promiscuous mode enabled
Feb 13 13:06:30 nas kernel: bridge0: link state changed to UP
Feb 13 13:06:30 nas kernel: bridge0: link state changed to UP
Feb 13 13:06:30 nas epair0a: Ethernet address: 02:c0:95:00:0e:0a
Feb 13 13:06:30 nas epair0b: Ethernet address: 02:c0:95:00:0f:0b
Feb 13 13:06:30 nas kernel: epair0a: link state changed to UP
Feb 13 13:06:30 nas kernel: epair0a: link state changed to UP
Feb 13 13:06:30 nas kernel: epair0b: link state changed to UP
Feb 13 13:06:30 nas kernel: epair0b: link state changed to UP
Feb 13 13:06:30 nas kernel: epair0a: promiscuous mode enabled
Feb 13 13:06:30 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 13 13:06:30 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 13 13:07:06 nas notifier: Performing sanity check on nginx configuration:
Feb 13 13:07:06 nas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Feb 13 13:07:06 nas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Feb 13 13:07:15 nas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://XX.XX.XX.XX/plugins/owncloud/1/_s/treemenu: timed out
Feb 13 13:08:52 nas manage.py: [plugins.utils:91] Couldn't retrieve http://XX.XX.XX.XX/plugins/owncloud/1/_s/status: No JSON object could be decoded
Feb 13 13:09:14 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.2
Feb 13 13:09:24 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.2
Feb 13 13:09:37 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.2
Feb 13 13:09:40 nas warden: Building new Jail... Please wait...
Feb 13 13:09:40 nas warden: zfs clone POOL1/jails/.warden-template-pluginjail@clean POOL1/jails/s3cmd_1
Feb 13 13:09:41 nas warden: Success!
Feb 13 13:09:41 nas warden: Jail created at /mnt/POOL1/jails/s3cmd_1
Feb 13 13:09:41 nas epair1a: Ethernet address: 02:e2:ae:00:0f:0a
Feb 13 13:09:41 nas epair1b: Ethernet address: 02:e2:ae:00:10:0b
Feb 13 13:09:41 nas kernel: epair1a: link state changed to UP
Feb 13 13:09:41 nas kernel: epair1a: link state changed to UP
Feb 13 13:09:41 nas kernel: epair1b: link state changed to UP
Feb 13 13:09:41 nas kernel: epair1b: link state changed to UP
Feb 13 13:09:41 nas kernel: epair1a: promiscuous mode enabled
Feb 13 13:09:41 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Feb 13 13:09:41 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Feb 13 13:09:51 nas notifier: Performing sanity check on nginx configuration:
Feb 13 13:09:51 nas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Feb 13 13:09:51 nas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Feb 13 13:10:03 nas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://XX.XX.XX.XX/plugins/owncloud/1/_s/treemenu: timed out
Feb 13 13:10:03 nas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/2/_s/treemenu: timed out
Feb 13 13:12:28 nas manage.py: [plugins.utils:91] Couldn't retrieve http://XX.XX.XX.XX/plugins/owncloud/1/_s/status: No JSON object could be decoded
Feb 13 13:12:28 nas manage.py: [plugins.utils:91] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/2/_s/status: No JSON object could be decoded
Feb 13 13:14:31 nas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://XX.XX.XX.XX/plugins/owncloud/1/_s/treemenu: timed out
Feb 13 13:14:31 nas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/2/_s/treemenu: timed out
Feb 13 13:15:55 nas manage.py: [plugins.utils:91] Couldn't retrieve http://XX.XX.XX.XX/plugins/owncloud/1/_s/status: No JSON object could be decoded
Feb 13 13:15:55 nas manage.py: [plugins.utils:91] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/2/_s/status: No JSON object could be decoded

 

[SteffanCline]

In looking at this I tried the command it suggested.
https://bugs.pcbsd.org/issues/4638
I saw some old IPs not in use that. I looked at the code in the file /etc/ix.rc.d/ix-plugins and it appears to draw it's configs from a SQLite table. Is there a way to clear those entries out?

 

[SteffanCline]

I've exhausted all options other than a wipe and reinstall. File a bug?

 

[SweetAndLow]

Your networking probably isn't configured. Double check that you have setup a default gateway and DNS for freenas.

 

[SteffanCline]

I just checked it again via the Network Summary and it's correct. All functions of FreeNAS are working as expected with the exception of these plugins. I'm connected to the web interface with no issues at all via a global IP. What else do you suggest checking?

 

[SweetAndLow]

I'm out of ideas

 

[SteffanCline]

I wish I could figure out what's causing these timeouts as they seem to be the culprit. Also, not sure why it's pinging this 192.168.0.1 as that IP is not registered or in use anywhere. It's either 199.249.xxx.1 or 192.168.1.X but clearly no router for the 192.168.1.0/24. Seems like something in the right direction.

Feb 17 09:54:54 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.1
Feb 17 09:54:58 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.1
Feb 17 09:55:11 nas manage.py: [common.pipesubr:71] Popen()ing: /sbin/ping -q -t 2 -o 192.168.0.1
Feb 17 09:55:14 nas warden: Building new Jail... Please wait...
Feb 17 09:55:14 nas warden: zfs clone POOL1/jails/.warden-template-pluginjail@clean POOL1/jails/s3cmd_1
Feb 17 09:55:15 nas warden: Success!
Feb 17 09:55:15 nas warden: Jail created at /mnt/POOL1/jails/s3cmd_1
Feb 17 09:55:15 nas bridge0: Ethernet address: 02:9d:b1:88:b2:00
Feb 17 09:55:15 nas kernel: bce0: promiscuous mode enabled
Feb 17 09:55:15 nas kernel: bridge0: link state changed to UP
Feb 17 09:55:15 nas kernel: bridge0: link state changed to UP
Feb 17 09:55:15 nas epair0a: Ethernet address: 02:c0:30:00:0e:0a
Feb 17 09:55:15 nas epair0b: Ethernet address: 02:c0:30:00:0f:0b
Feb 17 09:55:15 nas kernel: epair0a: link state changed to UP
Feb 17 09:55:15 nas kernel: epair0a: link state changed to UP
Feb 17 09:55:15 nas kernel: epair0b: link state changed to UP
Feb 17 09:55:15 nas kernel: epair0b: link state changed to UP
Feb 17 09:55:15 nas kernel: epair0a: promiscuous mode enabled
Feb 17 09:55:15 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 17 09:55:15 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 17 09:55:26 nas notifier: Performing sanity check on nginx configuration:
Feb 17 09:55:26 nas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Feb 17 09:55:26 nas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Feb 17 09:55:33 nas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/1/_s/treemenu: timed out
Feb 17 10:00:26 nas manage.py: [freeadmin.navtree:567] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/1/_s/treemenu: timed out
Feb 17 10:00:40 nas manage.py: [plugins.utils:91] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/1/_s/status: No JSON object could be decoded
Feb 17 10:01:56 nas manage.py: [plugins.utils:91] Couldn't retrieve http://XX.XX.XX.XX/plugins/s3cmd/1/_s/status: No JSON object could be decoded