perfsonar-user - Re: [perfsonar-user] host allegedly not globally registered
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Antoine Delvaux <>
- To: "Dale W. Carder" <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] host allegedly not globally registered
- Date: Wed, 25 Mar 2015 18:47:35 +0000
- Accept-language: fr-BE, en-US
- Authentication-results: wisc.edu; dkim=none (message not signed) header.d=none;
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?
Thank you,
Antoine.
> 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
- [perfsonar-user] host allegedly not globally registered, Dale W. Carder, 03/25/2015
- Re: [perfsonar-user] host allegedly not globally registered, Antoine Delvaux, 03/25/2015
- Re: [perfsonar-user] host allegedly not globally registered, Dale W. Carder, 03/25/2015
- Re: [perfsonar-user] host allegedly not globally registered, Aaron Brown, 03/25/2015
- Re: [perfsonar-user] host allegedly not globally registered, Dale W. Carder, 03/25/2015
- Re: [perfsonar-user] host allegedly not globally registered, Antoine Delvaux, 03/25/2015
Archive powered by MHonArc 2.6.16.