Firefly GUI does not show under the plug-in section

Status
Not open for further replies.

dkassman

Cadet
Joined
Feb 23, 2013
Messages
6
Problem: The Firefly plug-in does not show under the plug-in section of the left side menu. While it does appear in the list of Installed plugins the service will not turn on.

Description:
I recently upgraded from 9.1 to 9.2.0 and then I installed Firefly from the FreeNAS GUI. While Firefly appears to have installed correctly its icon does not show under the plug-in section of the left side menu, which means I cannot reach its configuration dialog. Instead, /var/log/messages has:


Code:
Dec 31 12:50:27 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/treemenu: timed out
Dec 31 12:50:42 freenas dhclient: New IP Address (em0): 192.168.2.2
Dec 31 12:50:42 freenas dhclient: New Subnet Mask (em0): 255.255.255.0
Dec 31 12:50:42 freenas dhclient: New Broadcast Address (em0): 192.168.2.255
Dec 31 12:50:42 freenas dhclient: New Routers (em0): 192.168.2.1
Dec 31 12:51:49 freenas manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/status: HTTP Error 504: Gateway Time-out
Dec 31 12:58:42 freenas manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/status: HTTP Error 504: Gateway Time-out
Dec 31 13:14:33 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/treemenu: timed out
Dec 31 13:16:06 freenas manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/status: HTTP Error 504: Gateway Time-out
Jan  1 12:43:03 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/treemenu: timed out
Jan  1 12:44:11 freenas manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/status: HTTP Error 504: Gateway Time-out
Jan  1 13:58:29 freenas manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.2.2/plugins/firefly/1/_s/status: HTTP Error 504: Gateway Time-out



Firefly is in the list of Installed plugins (it is the only one) but the service will not turn on either.
All of the instructions say to install the plug-in and its configuration UI will appear in the left menu. I deleted and reloaded Firefly but the results are the same.

HW/OS configuration
-------------------
Build: FreeNAS-9.2.0-RELEASE-x64 (ab098f4) (Just upgraded from a fresh 9.1 install)
Platform: Intel(R) Celeron(R) CPU G540 @ 2.50GHz
Memory: 16256MB
Browser: Firefox 26

NW information
----------------------
Code:
root@freenas> ifconfig

em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150
0                                                                               
        options=42098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO> 
        ether 70:54:d2:1a:ec:9f                                                 
        inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255             
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>                    
        media: Ethernet autoselect (1000baseT <full-duplex>)                    
        status: active                                                          
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536                      
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>                    
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 0x5                              
        inet 127.0.0.1 netmask 0xff000000                                       
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>                               
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500   
        ether 02:aa:dd:89:8c:00                                                 
        nd6 options=1<PERFORMNUD>                                               
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15             
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200                
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0                
        member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> 
         options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>                   
        inet6 ::1 prefixlen 128                                                 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5                              
        inet 127.0.0.1 netmask 0xff000000                                       
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>                               
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500   
        ether 02:aa:dd:89:8c:00                                                 
        nd6 options=1<PERFORMNUD>                                               
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15             
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200                
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0                
        member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>           
                ifmaxaddr 0 port 7 priority 128 path cost 2000                  
        member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>               
                ifmaxaddr 0 port 1 priority 128 path cost 20000                 
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
 1500                                                                           
        options=8<VLAN_MTU>                                                     
        ether 02:b1:cb:00:07:0a                                                 
        inet6 fe80::b1:cbff:fe00:70a%epair0a prefixlen 64 scopeid 0x7           
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>                               
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)                     
        status: active   



Plug-ins
--------
Name: Firefly
Version: 1696_8
PBI: firefly-1696_8-amd64

Jails
-----
Name: firefly_1
IPv4 address: 192.168.2.14
Netmask: /24 (255.255.255.0)
Autostart: enabled
VIMAGE: enabled



Code:
[root@freenas ~]# jls                                                           
   JID  IP Address      Hostname                      Path                      
     2  -               firefly_1                     /mnt/Volume1/jails/firefly
_1
                                                                             
[root@freenas ~]# jexec 2 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>                               
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500   
        options=8<VLAN_MTU>                                                     
        ether 02:43:53:00:08:0b                                                 
        inet 192.168.1.14 netmask 0xffffff00 broadcast 192.168.1.255            
        inet6 fe80::43:53ff:fe00:80b%epair0b prefixlen 64 tentative scopeid 0x2 
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>                    
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)                     
        status: active              


 
D

dlavigne

Guest
Is it just firefly that doesn't show up or is it any plugin? If it's any plugin, there's a IP addressing problem somewhere.
 

dkassman

Cadet
Joined
Feb 23, 2013
Messages
6
Firefly was the only plugin loaded so I added the Plex Media Server. I got the same results so it looks like an IP addressing problem (which I suspected) but I am not sure how to diagnose the issue or where to look further; I don't see anything funny when I review the results of the commands I posted.
 

N00b

Explorer
Joined
May 31, 2013
Messages
83
I don't have firefly installed but try unchecking VIMAGE. I have not been able to run my jails with VIMAGE enabled. Not sure if this the right was to do it but I can get jail network (bridged) to work with VIMAGE unchecked.
 

dkassman

Cadet
Joined
Feb 23, 2013
Messages
6
I don't have firefly installed but try unchecking VIMAGE. I have not been able to run my jails with VIMAGE enabled. Not sure if this the right was to do it but I can get jail network (bridged) to work with VIMAGE unchecked.
Tried VIMAGE unchecked and it did not make any difference. :(
 
Joined
Jun 17, 2013
Messages
36
Same issue. Un-checking VIMAGE doesn't fix it.

It appears to occur only on boxes that have two NICs where I am using an IP address from the range of the second NIC.
 
D

dlavigne

Guest
It appears to occur only on boxes that have two NICs where I am using an IP address from the range of the second NIC.

Is this using Plugins or Jails? I don't think Plugins supports multiple address ranges but Jails should.
 

dkassman

Cadet
Joined
Feb 23, 2013
Messages
6
When I installed my plug-ins FreeNAS created a jail for each. Since I am running a single NIC multiple address ranges is not causing my issues, but I still am no closer to solving my problem.
 
Joined
Jun 17, 2013
Messages
36
Is this using Plugins or Jails? I don't think Plugins supports multiple address ranges but Jails should.


Not sure which it falls under. In the jail configuration I set an IP range from the subnet of my second NIC. I haven't tried running 'just a jail', it's always been a plugin like btsync.
 

Dalamar81

Cadet
Joined
Apr 6, 2014
Messages
2
I had the same problem with btsync_1 after adding second NIC to the FreeNAS host.
It was revealed, that nameservers, configured with web interface was disappeared from /etc/resolv.conf.
I resolved this by changing nameservers with GUI to wrong values and reverting them to original values. After that nameservers appeared in /etc/resolv.conf. After rebooting plugin became accessible.
 
Status
Not open for further replies.
Top