Plugin - service status not working

[WillD]

Fresh install of FreeNAS-9.2.1.2-RELEASE-x64

New install of Plugin crash plan version 3.6.3_1-amd64
New install of Plugin owncloud version 6.0.1

I'm not able to "Turn On" the service status button in for crashplan plugin and owncloud plugin. The jails are running properly and I'm able to confirm it has full connectivity to the network, gateway and other devices on the same subnet. I have confirmed the network is configured correct and both boxes can see the gateway.

I'm getting the following errors...
Mar 13 14:50:09 nas manage.py: [plugins.utils:92] Couldn't retrieve https://10.1.1.17/plugins/crashplan/1/_s/status: HTTP Error 502: Bad Gateway
Mar 13 14:51:09 nas manage.py: [plugins.utils:92] Couldn't retrieve https://10.1.1.17/plugins/owncloud/2/_s/status: HTTP Error 504: Gateway Time-out
Mar 13 14:57:16 nas manage.py: [plugins.utils:92] Couldn't retrieve https://10.1.1.17/plugins/crashplan/1/_s/status: HTTP Error 502: Bad Gateway
Mar 13 14:58:16 nas manage.py: [plugins.utils:92] Couldn't retrieve https://10.1.1.17/plugins/owncloud/2/_s/status: HTTP Error 504: Gateway Time-out

I'm also noticing lag/slow response when opening up the plugins installed tab.

any info will help. I'm thankful for your response.

 

[dlavigne]

Does following the instructions at the bottom of this comment fix it?

 

[Lusca]

got same issue , but with cp and sab...
The comment u linked did not work for me.. :( still always off

Code:

Mar 15 15:06:23 freenas kernel: arp: 02:52:26:00:0d:0a is using my IP address 192.168.1.191 on epair5b!
Mar 15 15:06:26 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.1.220/plugins/couchpotato/1/_s/treemenu: HTTP Error 502: Bad Gateway
Mar 15 15:06:26 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.1.220/plugins/sabnzbd/2/_s/treemenu: HTTP Error 502: Bad Gateway
Mar 15 15:09:17 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/couchpotato/1/_s/status: HTTP Error 502: Bad Gateway
Mar 15 15:09:17 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/sabnzbd/2/_s/status: HTTP Error 502: Bad Gateway
Mar 15 15:18:58 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.1.220/plugins/couchpotato/1/_s/treemenu: HTTP Error 502: Bad Gateway
Mar 15 15:18:58 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.1.220/plugins/sabnzbd/2/_s/treemenu: HTTP Error 502: Bad Gateway

 

[dlavigne]

Mar 15 15:06:23 freenas kernel: arp: 02:52:26:00:0d:0a is using my IP address 192.168.1.191 on epair5b!

That looks like an ARP issue. Try running arp -da from Shell.

 

[Lusca]

I did a reinstall of cp and sab.. works like charm.



for now.

 

[Lusca]

ah well... had a power out an hour ago...

restarted the freenas now, and back to : sick and sab down....same error "some error occured"..

last bit from boot shell : bit wall of text..but might be some clues in the top?

Code:

Mar 16 23:27:16 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Mar 16 23:27:16 freenas last message repeated 2 times
Mar 16 23:27:17 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 freenas.local. (Addr) that's already in the list
Mar 16 23:27:17 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 220.1.168.192.in-addr.arpa. (PTR) that's already in the list
Mar 16 23:27:19 freenas kernel: bridge0: link state changed to UP
Mar 16 23:27:19 freenas kernel: em0: promiscuous mode enabled
Mar 16 23:27:19 freenas kernel: epair0a: link state changed to UP
Mar 16 23:27:19 freenas kernel: epair0b: link state changed to UP
Mar 16 23:27:19 freenas kernel: em0: link state changed to DOWN
Mar 16 23:27:19 freenas kernel: epair0a: promiscuous mode enabled
Mar 16 23:27:21 freenas kernel: em0: link state changed to UP
Mar 16 23:27:26 freenas kernel: epair1a: link state changed to UP
Mar 16 23:27:26 freenas kernel: epair1b: link state changed to UP
Mar 16 23:27:26 freenas kernel: epair1a: promiscuous mode enabled
Mar 16 23:27:31 freenas kernel: epair2a: link state changed to UP
Mar 16 23:27:31 freenas kernel: epair2b: link state changed to UP
Mar 16 23:27:31 freenas kernel: epair2a: promiscuous mode enabled
Mar 16 23:27:34 freenas root: /etc/rc: WARNING: Could not start sabnzbd_1
Mar 16 23:27:36 freenas kernel: epair3a: promiscuous mode enabled
Mar 16 23:27:39 freenas root: /etc/rc: WARNING: Could not start sickbeard_1
Mar 16 23:27:40 freenas kernel: epair4a: promiscuous mode enabled
Mar 16 23:28:01 freenas dhclient: New IP Address (em0): 192.168.1.220
Mar 16 23:28:01 freenas dhclient: New Subnet Mask (em0): 255.255.255.0
Mar 16 23:28:01 freenas dhclient: New Broadcast Address (em0): 192.168.1.255
Mar 16 23:28:01 freenas dhclient: New Routers (em0): 192.168.1.1
Mar 16 23:28:15 freenas ntpd_initres[11276]: host name not found: 0.freebsd.pool.ntp.org
Mar 16 23:28:31 freenas ntpd_initres[11276]: host name not found: 1.freebsd.pool.ntp.org
Mar 16 23:28:47 freenas ntpd_initres[11276]: host name not found: 2.freebsd.pool.ntp.org
Mar 16 23:29:56 freenas kernel: em0: link state changed to DOWN
Mar 16 23:29:59 freenas kernel: em0: link state changed to UP
Mar 16 23:30:35 freenas dhclient: New IP Address (em0): 192.168.1.220
Mar 16 23:30:35 freenas dhclient: New Subnet Mask (em0): 255.255.255.0
Mar 16 23:30:35 freenas dhclient: New Broadcast Address (em0): 192.168.1.255
Mar 16 23:30:35 freenas dhclient: New Routers (em0): 192.168.1.1
Mar 16 23:30:51 freenas ntpd_initres[11276]: host name not found: 0.freebsd.pool.ntp.org
Mar 16 23:30:59 freenas ntpd_initres[11276]: host name not found: 1.freebsd.pool.ntp.org
Mar 16 23:34:12 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve https://192.168.1.220/plugins/sickbeard/3/_s/treemenu: HTTP Error 502: Bad Gateway
Mar 16 23:34:12 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve https://192.168.1.220/plugins/sabnzbd/6/_s/treemenu: HTTP Error 502: Bad Gateway
Mar 16 23:34:50 freenas manage.py: [plugins.utils:92] Couldn't retrieve https://192.168.1.220/plugins/sickbeard/3/_s/status: HTTP Error 502: Bad Gateway
Mar 16 23:34:55 freenas manage.py: [plugins.utils:92] Couldn't retrieve https://192.168.1.220/plugins/sabnzbd/6/_s/status: HTTP Error 502: Bad Gateway

 

[Lusca]

yeah so.. now it suddenly just deleted my movie folder...gg .. gotta say I love theese 4 days of freenas ...

 

[Lusca]

Back up and running smooth again.
Is it possible to use snapshot of the entire volume or only jails, so I could run the rollback on jails to get it back and running without the whole process of deleting, installing plugins and reconfigure them?

 

[cyberjock]

Back up and running smooth again.
Is it possible to use snapshot of the entire volume or only jails, so I could run the rollback on jails to get it back and running without the whole process of deleting, installing plugins and reconfigure them?

Sure.

 

[WillD]

Back up and running smooth again.
Is it possible to use snapshot of the entire volume or only jails, so I could run the rollback on jails to get it back and running without the whole process of deleting, installing plugins and reconfigure them?

What did you do to fix it? I'm still experiencing the same problem.

 

[Lusca]

reinstall plugins...

 

[WillD]

reinstall plugins...

Even if i install a new pluggin i still get the same problem.

 

[SkyMonkey]

Having this same issue in 9.2.1.3 (and in the previous two 9.2.1.x releases).

 

[marcevan]

This has persisted as 500 or 502 errors regardless of the removal of vimage.

Though unchecking vimage gave me back Plex, Transmission just keeps on 500'ing.

Something else besides delete plugin and reinstall please. Seems to be a linkage between plugin and jail that gets tweaked in how manage.py does treemenu because the table for plugin_plugins works properly show the installed plugins view and the plugin itself works.

 

[SkyMonkey]

Unchecking vimage lets Transmission start (apparently) on my machine, but I still cannot get to the gui. Could be a combination of this and other networking issues (that I've not bothered to troubleshoot since the 9.2.1.x branch is giving me all sorts of samba issues, and I'm waiting on that to be fixed first).

 

[SkyMonkey]

Still having this issue after upgrading to 9.2.1.6.

Installing minidlna gives the following in the console:

Code:

Aug 5 21:14:42 freenas manage.py: [common.pipesubr:58] Popen()ing: /sbin/ping -q -t 2 -o 192.168.25.1
Aug 5 21:14:46 freenas manage.py: [common.pipesubr:58] Popen()ing: /sbin/ping -q -t 2 -o 192.168.25.1
Aug 5 21:15:36 freenas manage.py: [common.pipesubr:58] Popen()ing: /sbin/ping -q -t 2 -o 192.168.25.1
Aug 5 21:15:38 freenas warden: Building new Jail... Please wait...
Aug 5 21:15:38 freenas warden: zfs clone bluemesa/jails/.warden-template-pluginjail@clean bluemesa/jails/minidlna_1
Aug 5 21:15:40 freenas warden: Success!
Aug 5 21:15:40 freenas warden: Jail created at /mnt/bluemesa/jails/minidlna_1
Aug 5 21:15:40 freenas kernel: bridge0: Ethernet address: 02:42:f1:2d:9e:00
Aug 5 21:15:40 freenas kernel: bridge0: link state changed to UP
Aug 5 21:15:40 freenas kernel: em0: promiscuous mode enabled
Aug 5 21:15:40 freenas kernel: epair0a: Ethernet address: 02:b8:e7:00:08:0a
Aug 5 21:15:40 freenas kernel: epair0b: Ethernet address: 02:b8:e7:00:09:0b
Aug 5 21:15:40 freenas kernel: epair0a: link state changed to UP
Aug 5 21:15:40 freenas kernel: epair0b: link state changed to UP
Aug 5 21:15:40 freenas kernel: em0: link state changed to DOWN
Aug 5 21:15:40 freenas kernel: epair0a: promiscuous mode enabled
Aug 5 21:15:40 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Aug 5 21:15:44 freenas kernel: em0: link state changed to UP
Aug 5 21:15:55 freenas notifier: Performing sanity check on nginx configuration:
Aug 5 21:15:55 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Aug 5 21:15:55 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Aug 5 21:16:01 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.42.70/plugins/minidlna/1/_s/treemenu: timed out

Upon clicking the installed plugins tab, it takes quite some time to load, and then shows the plugin as off. This appears in the console:

Code:

Aug 5 21:17:12 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.42.70/plugins/minidlna/1/_s/status: HTTP Error 504: Gateway Time-out

 

[SkyMonkey]

I've stopped the jail, and put my local router address into the IPv4 default gateway (it was empty). VIMAGE is checked, NAT is not.

No change, behaviors. Attempting to turn the plugin on results in a long wait (~60 sceconds or so) and a "Some error occurred" message banner appearing.

 

[SkyMonkey]

I found that the jail template (and therefore created jails) IP range was outside my local subnet. I fixed this and the problem is now (seemingly) solved.

 

[Bob Parr]

I tried to delete the plugin, but I get a message stating, "Error: The plugins jail is not running, start it before proceeding".
However, when I attempt to start the plugin jail (setting the jail service status to ON?) I get the following error: "Some error occurred"
I tried reinstalling the plugin, but this did not work for me, and I keep getting the same errors. I'm missing something, but I don't know what it is or where to find it (or what to search on to find it).

Please assist!

 

[windyboi]

Anyone have any solution to this? I'm experiencing the same problem and this thread seems to have not reached a resolution.