No plugins list

[LearnLearnLearn]

Yup, I know, there are tons of threads about this problem but none seem to help.

Doesn't seem to be a network issue. I have dns entries in /etc/resolv.conf, nothing is blocked, can ping and resolve domain names, everyting networking works as it should including using curl.

I had LACP configured but the moment I installed the Plex media server, all hell broke loose. LACP broke and the server became unreachable. I had to disable LACP on the server and the switch so I could go back to single NIC which now works again.

After rebooting, I see the plex media server installed but it take something like a minute for it to show in the Installed list.

In the plugins repo url, I have; http://download.freenas.org/plugins/9/x64/pbi-meta/pbi-repo.rpo, yet, trying to get a list of plugins from the Plugins tab leads to nothing listed.

Something is broken and I doubt it's anything I've done since I've not done much with the server yet so, looking for ideas, things to try :)

Thanks.

 

[Apollo]

Freenas may not be able to access the web and it may never have since you installed it. What version of Freenas and hardware?
Can you see Freenas updates?

 

[LearnLearnLearn]

As mentioned, I've also tested using curl and can reach web and other things.

[root@freenas] ~# curl -m 5 -o /dev/null --silent --head --write-out '%{http_code}\n' http://www.google.com -o /dev/null
200


Since the system is fresh, there aren't any updates so far it seems.

FreeNAS 9.3 64-bit

MB SuperMicro (No idea, purchased machines as whole, Pivot3 CD-B units)
CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (2261.05-MHz K8-class CPU)
12GB memory - Kingston KVR1333D3D8R9S/2G
12 x Western Digital WD1002FBYS
4 built in GB NICs - Only one configured at this time

 

[Apollo]

You may have access to the internet from the shell, but does it guarantee Freenas itself can contact the server? Not sure.
If you manually check for updates, as long as it doesn't complain about not being able to reach the server then you should be fine.
It is possible the repository servers for the jails are down? just a guess.
Can you create a jail and install any of the packages manually? you can try Plex as it has a tutorial for CLI install.
Could it be your browser may be messing up with the Web GUI and prevent you from accessing the content of the page. Can you try another browser?

 

[LearnLearnLearn]

Hi,

Yes, I tried from another browser just to be safe, acts the same way.
Yes, from cli, I can ping and resolve internal and external domains and IPs.

Not sure what you mean by manually updating? There aren't any updates that I know of.
From the GUI, going to Update and clicking on 'check now', it does respond with 'No updates available' which seems to imply it is reaching the repo.
Using the 'Verify Install' gives 'All files verified successfully'.

When I check for plugins it shows 'Loading...' and eventually the result is 'No entry has been found'.

I tried another testing from the server cli using curl.

[root@freenas] ~# curl -m 5 -o /dev/null --silent --head --write-out '%{http_code}\n' http://www.google.com -o /dev/null
200
[root@freenas] ~# curl -m 5 -o /dev/null --silent --head --write-out '%{http_code}\n' http://download.freenas.org/plugins/9/x64/pbi-meta/pbi-repo.rpo -o /dev/null
000
[root@freenas] ~# curl -o /dev/null --silent --head --write-out '%{http_code}\n' http://download.freenas.org/plugins/9/x64/pbi-meta/pbi-repo.rpo -o /dev/null
200

Notice that when I took the timeout option out, then I eventually get a response of 200 for the repo.

 

[Apollo]

Hi,
Not sure what you mean by manually updating? There aren't any updates that I know of.
From the GUI, going to Update and clicking on 'check now', it does respond with 'No updates available' which seems to imply it is reaching the repo.

This is what I meant. So Freenas does get access to the update server.

When I check for plugins it shows 'Loading...' and eventually the result is 'No entry has been found'.

I tried another testing from the server cli using curl.

[root@freenas] ~# curl -m 5 -o /dev/null --silent --head --write-out '%{http_code}\n' http://www.google.com -o /dev/null
200
[root@freenas] ~# curl -m 5 -o /dev/null --silent --head --write-out '%{http_code}\n' http://download.freenas.org/plugins/9/x64/pbi-meta/pbi-repo.rpo -o /dev/null
000
[root@freenas] ~# curl -o /dev/null --silent --head --write-out '%{http_code}\n' http://download.freenas.org/plugins/9/x64/pbi-meta/pbi-repo.rpo -o /dev/null
200

Notice that when I took the timeout option out, then I eventually get a response of 200 for the repo.

I suspect you have a latency issue, just an educated guess as you are reporting a timeout issue., or a network collision.

 

[LearnLearnLearn]

Seems to be a problem reaching the freenas site...

[root@freenas] ~# ping download.freenas.org
PING download.freenas.org (64.62.136.38): 56 data bytes
^C
--- download.freenas.org ping statistics ---
134 packets transmitted, 0 packets received, 100.0% packet loss

[root@freenas] ~# ping www.google.com
PING www.google.com (173.194.33.180): 56 data bytes
64 bytes from 173.194.33.180: icmp_seq=0 ttl=54 time=53.069 ms
64 bytes from 173.194.33.180: icmp_seq=1 ttl=54 time=47.357 ms
^C
--- www.google.com ping statistics ---
3 packets transmitted, 2 packets received, 33.3% packet loss
round-trip min/avg/max/stddev = 47.357/50.213/53.069/2.856 ms

[root@freenas] ~# ping www.petsmart.com
PING www.petsmart.com.ssopt.net (74.217.214.123): 56 data bytes
64 bytes from 74.217.214.123: icmp_seq=0 ttl=53 time=31.992 ms
64 bytes from 74.217.214.123: icmp_seq=1 ttl=53 time=31.385 ms
^C
--- www.petsmart.com.ssopt.net ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 31.385/31.689/31.992/0.304 ms

 

[Apollo]

Not just Freenas, google too.

 

[LearnLearnLearn]

Actually, freenas.org or download.freenas.org, either should respond since they are FQDN but neither do.

[root@freenas] ~# ping download.freenas.org
PING download.freenas.org (64.62.136.38): 56 data bytes
^C
--- download.freenas.org ping statistics ---
134 packets transmitted, 0 packets received, 100.0% packet loss

[root@freenas] ~# ping freenas.org
PING freenas.org (64.62.136.60): 56 data bytes
^C
--- freenas.org ping statistics ---
76 packets transmitted, 0 packets received, 100.0% packet loss

 

[Apollo]

Actually, freenas.org or download.freenas.org, either should respond since they are FQDN but neither do.

[root@freenas] ~# ping download.freenas.org
PING download.freenas.org (64.62.136.38): 56 data bytes
^C
[root@freenas] ~# ping freenas.org
PING freenas.org (64.62.136.60): 56 data bytes
^C
--- freenas.org ping statistics ---
76 packets transmitted, 0 packets received, 100.0% packet loss

I have the same behavior when ping freenas using your ping command.
Maybe iXsytem is to blame.

 

[LearnLearnLearn]

Maybe it just doesn't respond to icmp

~# nslookup freenas.org
Server: 192.168.1.29
Address: 192.168.1.29#53

Non-authoritative answer:
Name: freenas.org
Address: 64.62.136.60

[root@freenas] ~# curl download.freenas.org
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<title>Index of /</title>
</head>
<body>

 

[LearnLearnLearn]

So, this is nothing but odd now. Assuming download.freenas.org simply doesn't respond to icmp, that's one thing.
I can nslookup and get an instant resolve of the domain name.
I can use curl and get an instant response from the domain name.

Yet, from the Plugins menu, it never shows a list.

 

[LearnLearnLearn]

I'm watching outgoing port 80/443 connections while I click on Plugins and refresh and there aren't ever any attempts to connect to
download.freenas.org.

 

[mjws00]

If you click the plugins button at the top. You may get a traceback... there is an issue when no jail storage is configured. https://bugs.pcbsd.org/issues/9294

So build a jail. Give it storage. Then try again.

Also you said you can build a jail. So you might be better off installing there from pkg. There are lots of advantages... the downside is it requires reading.

 

[LearnLearnLearn]

The plex server is running, has it's storage, etc. When I installed plex, I was using LACP networking at the time which seemed to be related to losing network access. I had to remove that config, go back to individual nics for now and all started working but the plugins list.

That's where I'm at now. The plex server is there, accessible, running, etc.

Looking in the logs, I am not seeing any errors when trying to get the plugins list.
I think something is wrong with the plugins list code. When I clicked on it after having built the new server, I got a bunch of errors. I think related to this since it was similar errors.

https://bugs.pcbsd.org/issues/9227

 

[mjws00]

If it was my box, I'd do a clean install on a fresh usb. Possibly even a few updates back. You can import the pool. You can always plug in the stick that doesn't work.

Get a known good baseline, then worry about adding all the junk. One variable at a time is the name of the game.

 

[LearnLearnLearn]

I didn't add any junk. I was only checking Plugins after running the box for a while. There were no issues,
It was a good baseline before I clicked on Plugins :)

Still is, everything is working but Plugins. Even the now installed Plex is working. Just can't get a list of Plugins. I've already been using it for esx hosting as well so can't go rebuilding for such a small bug.

 

[LearnLearnLearn]

Days later, it's still showing 'No entry has been found'

 

[Apollo]

Days later, it's still showing 'No entry has been found'

Any improvements?
Can you check whether the following file contains something similar:

/etc/resolv.conf

Code:

# Generated by resolvconf
search localdomain
nameserver 192.168.1.1

I have been playing around with jails, and one of the reason they would not register on the network or get updates would be because either the "nameserver x.x.x.x" is not there or it is not set to the proper subnet address.

 

[LearnLearnLearn]

I thought I posted those things but yes, resolve works fine but for the plugins site.
Yes, my /etc/resolv.conf was populated hence, dns resolves were working.

I just tried plugins now and it works. I've not changed a single thing since the last time we looked at this. I had decided not to use this server for anything but iSCSI, NFS and CIFS shares, no plugins etc. I ordered another server so I can play with the rest of the system without taking anything down.