Freenas 9.2.0 - No plugins showing on Plugin Page

[shackrock]

Hi all, just upgraded to Freenas 9.2.0.

Take a look at what I see on the plugin page, the list of available plugins never loads.

Repo URL is the default: http://www.freenas.org/downloads/plugins/9/x64/pbi-meta/pbi-repo.rpo - and that seems to exist when I click that link.

These are the latest few errors showing in the console:

Code:

Jan 26 08:24:11 freenas notifier: Stopping avahi-daemon.
Jan 26 08:25:54 freenas ntpd_initres[2648]: host name not found: 0.freebsd.pool.ntp.org
Jan 26 08:25:54 freenas ntpd_initres[2648]: host name not found: 1.freebsd.pool.ntp.org
Jan 26 08:25:54 freenas ntpd_initres[2648]: host name not found: 2.freebsd.pool.ntp.org
Jan 26 08:29:56 freenas ntpd_initres[2648]: host name not found: 0.freebsd.pool.ntp.org
Jan 26 08:29:56 freenas ntpd_initres[2648]: host name not found: 1.freebsd.pool.ntp.org
Jan 26 08:29:56 freenas ntpd_initres[2648]: host name not found: 2.freebsd.pool.ntp.org

I deleted my Plex Jail and Plex Plugin before the upgrade. I was having some random issues with it and wanted to start fresh in 9.2.0.

Any ideas?
Thanks.

 

[DrKK]

Your problem is that you don't have a DNS (nameserver) set up correctly for the jail. Other than that, everything is fine.

I am not sure where a pbi jail like the one you have gets its DNS information from (I've never used a plugin jail with, presumably, its own network stack), but this is definitely a solved problem. You might go into global configuration, and under "nameserver", put something reasonable (either the address of your router---which usually has its own DNS---or something like 8.8.8.8 which is Google's DNS).

In any case, you now know the nature of the problem, and judicious use of google and forum search should get it done from this point.

 

[shackrock]

Hm, I've tried a lot of that, no luck with it. I'll continue on this thread: http://forums.freenas.org/threads/plugins-not-showing-up-no-entry-has-been-found.17330/

 

[Dusan]

The root cause can easily be that your NAS is unable to reach internet (so nothing works, including DNS). Can you ping any internet address from FreeNAS shell? Try "ping 8.8.8.8".

 

[shackrock]

Yep no problem there:

Code:

[root@freenas ~]# ping 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=47 time=26.159 ms                       
64 bytes from 8.8.8.8: icmp_seq=1 ttl=47 time=26.536 ms                       
64 bytes from 8.8.8.8: icmp_seq=2 ttl=47 time=26.239 ms                       
64 bytes from 8.8.8.8: icmp_seq=3 ttl=47 time=26.320 ms                       
64 bytes from 8.8.8.8: icmp_seq=4 ttl=47 time=26.242 ms                       
64 bytes from 8.8.8.8: icmp_seq=5 ttl=47 time=25.943 ms                       
64 bytes from 8.8.8.8: icmp_seq=6 ttl=47 time=31.894 ms                       
64 bytes from 8.8.8.8: icmp_seq=7 ttl=47 time=26.384 ms                       
^C                                                                             
--- 8.8.8.8 ping statistics ---                                               
9 packets transmitted, 8 packets received, 11.1% packet loss                   
round-trip min/avg/max/stddev = 25.943/26.965/31.894/1.870 ms

 

[DrKK]

So again, you don't have a DNS server (nameserver). You may have to manually hack /etc/resolv.conf.

 

[shackrock]

So again, you don't have a DNS server (nameserver). You may have to manually hack /etc/resolv.conf.

Why do you say I don't have one? I have two listed.

 

[DrKK]

No, I understand that you have them listed in there, but they are NOT being used. Check the actual physical contents of the /etc/resolv.conf file, and tell us what it says.

 

[shackrock]

No, I understand that you have them listed in there, but they are NOT being used. Check the actual physical contents of the /etc/resolv.conf file, and tell us what it says.

Here it is:

Code:

search local
nameserver 8.8.8.8
nameserver 8.8.4.4

I wonder if it's possible to reset all network settings to factory default again, maybe something is weird in here after my upgrade to 9.2?

 

[shackrock]

UPDATE:

Ok, so this morning I was clicking around, and in interfaces I saw that my DHCP was unclicked for some reason. I put it back on, hit save, then restarted the server. After that, everything is functional (I also left the 8.8.8.8 / 8.8.4.4 nameservers in as well though). Now, everything seems to be back to normal. Hopefully this is a fix for everyone else w/this problem as well.

Thanks for all the help.

 

[Supa]

I'm actually having the same problem. Getting various results. Will report back later. My DHCP is already checked too.

 

[Paralyzing Agent]

I found the same trouble after setting my IPv4 address when I set the reservation on my router. DHCP was disabled, and thus the IPv4 Default Address needed to be set. After a reboot, I was good to go.