perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Dale,

It looks like the lookup service was defaulting to only listening on v4. I’ve 
mucked with the startup script, and now it seems to be listening on v4 and v6.

Cheers,
Aaron

> On Mar 25, 2015, at 4:16 PM, Dale W. Carder 
> <>
>  wrote:
> 
> Thus spake Antoine Delvaux 
> ()
>  on Wed, Mar 25, 2015 at 06:47:35PM +0000:
>> Hi Dale,
>> 
>> If your host appears in the Services Directory 
>> http://stats.es.net/ServicesDirectory it actually is correctly registered.
>> 
>> An issue with the message "Globally registered: No" sometimes show when 
>> there is a discrepancy between the reverse DNS record for your host and 
>> the hostname that is registered with in the Services Directory.
>> 
>> This may also happen if your host is using multiple interfaces and that 
>> perfSONAR cannot reliably decide which interface is the primary.
>> 
>> Can you tell us which server we're talking about?
> 
> ndb1.internet2.edu
> 
> I note it has an AAAA record in DNS, but it appears not to have a working 
> server 
> listening on port 8090.  It does seem to work however for legacy protocols.
> 
>> telnet ndb1.internet2.edu 8090
> Trying 2001:48a8:68fe::66...
> telnet: connect to address 2001:48a8:68fe::66: Connection refused
> 
> So, I am curious if that is the source of the problem with verifying the
> registration.
> 
> Dale
> 
> 
>> 
>>> Le 25 mars 2015 à 15:05, Dale W. Carder 
>>> <>
>>>  a écrit :
>>> 
>>> 
>>> On a freshly upgraded perfsonar host, it says that it is not globally
>>> registered.  Interestingly, if I browse 
>>> http://stats.es.net/ServicesDirectory 
>>> I can find it.  Also there is nothing obvious (to me) in the logs about
>>> it being unable to register.
>>> 
>>> I queried 
>>> perfSONAR_PS::Utils::LookupService::discover_primary_lookup_service()
>>> and got: http://ndb1.internet2.edu:8090/lookup/records
>>> 
>>> So, I naively do:
>>> 
>>>> wget http://ndb1.internet2.edu:8090/lookup/records
>>> --2015-03-25 09:58:18--  http://ndb1.internet2.edu:8090/lookup/records
>>> Resolving ndb1.internet2.edu... 2001:48a8:68fe::66, 207.75.164.66
>>> Connecting to ndb1.internet2.edu|2001:48a8:68fe::66|:8090... failed: 
>>> Connection refused.
>>> Connecting to ndb1.internet2.edu|207.75.164.66|:8090... connected.
>>> HTTP request sent, awaiting response... 200 OK
>>> Length: unspecified [application/json]
>>> Saving to: “records”
>>> 2015-03-25 09:58:20 (7.00 MB/s) - “records” saved [6119457]
>>> 
>>> 
>>> I'm guessing that perfsonar doesn't implement something rfc6555-ish, and 
>>> this host refusing connections may be the source of my problem.
>>> 
>>> Dale
>>