perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

Just to expand upon that, the current perfSONAR project managed Lookup Service server runs behind a single IP hosted at Google cloud. This has been the case since fall of last year. If you are not allowing your host to contact that IP, then it cannot register in the centrally managed service. We are in the midst of evaluating both the current LS architecture and deployment model, so it is possible the location of the hosting may change in the future. For now, the few months we’ve had the current setup has greatly helped with stability issues we struggled with for years having the LS infrastructure and dataset fractured between sites and organizations. We fully realize there are many ways to tackle this issue and we are still looking at those, this was just the path of least resistance to curtail emails like this from being “LS server X is down (again)”. 

Thanks,

Andy

On June 19, 2019 at 12:00:43 PM, Pete Siemsen () wrote:

It happens that I was on a conference call later on Jun 17, and Andy Lake was on the call. He said the problem is understood, but there isn't a fix at the moment - there is only one LS server, and it's not visible on the research networks.

Does that mean that all perfsonars that hove connections only to the research network are unregistered?

-- Pete

On Mon, Jun 17, 2019 at 1:01 PM Pete Siemsen <> wrote:

Sowmya,

Thanks. Trouble is, the machine is connected to only research networks (I2, ESnet, etc) so it can't reach 35.237.255.214. Is there a URL I can use that is on the Internet2 or ESnet network?

-- Pete

On Fri, Jun 14, 2019 at 6:04 PM Sowmya Balasubramanian <> wrote:

Hi Pete,

From your logs, it looks like your LS URL is set to http://ps-east.es.net:8090/lookup/records. This LS instance is not being used as a global LS.

If you have set ls_instance in your conf file, please change it to http://35.237.255.214:8090/lookup/records and you should start seeing your records in the global LS instance.

Regards,

Sowmya

On Fri, Jun 14, 2019 at 4:40 PM Pete Siemsen <> wrote:

My freshly installed perfsonar won't globally register itself. I had this problem before, documented at https://lists.internet2.edu/sympa/arc/perfsonar-user/2018-07/msg00019.html

I found that old posting, and the solution it contains improved things this time, somewhat. My /var/log/perfsonar/lsregistrationdaemon.log is attached. It shows that things were really not working, and then after I applied Andy's fix, the logs messages look promising.

But I'm still not globally registered. Huh. The machine is perfsonar-1850.frgp.net.

-- Pete

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user