perfSONAR User Q&A and Other Discussion

[Pete Siemsen <>]

My brand new 4.0.2 perfsonar system won't register itself.

I have lots of these in /var/log/perfsonar/lsregistrationdaemon.log:

2018/08/03 16:02:14 (1904) ERROR> LookupService.pm:110 perfSONAR_PS::Utils::LookupService::discover_lookup_services - Problem retrieving http://ps1.es.net:8096/lookup/activehosts.json: 500 timeout

2018/08/03 16:02:14 (1904) WARN> lsregistrationdaemon.pl:144 main::__ANON__ - Warned: Use of uninitialized value $current_ls_instance in concatenation (.) or string at /usr/lib/perfsonar/bin/lsregistrationdaemon.pl line 257.

2018/08/03 16:02:14 (1904) INFO> lsregistrationdaemon.pl:257 main:: - Initial LS URL set to

2018/08/03 16:02:14 (1904) ERROR> lsregistrationdaemon.pl:301 main:: - Unable to determine ls_instance so not performing any operations

I can ping ps1.es.net.

I can traceroute:

perfsonar-1850$ traceroute ps1.es.net

traceroute to ps1.es.net (198.128.151.11), 30 hops max, 60 byte packets

 1  gateway (129.19.165.1)  0.243 ms  0.223 ms  0.216 ms

 2  denvcr5-frgp.es.net (198.129.248.125)  0.661 ms  0.719 ms  0.974 ms

 3  sacrcr5-ip-a-denvcr5.es.net (134.55.50.201)  21.552 ms  21.658 ms  22.718 ms

 4  esnetrt5-ip-a-sacrcr5.es.net (198.129.33.177)  24.507 ms  24.497 ms  24.519 ms

 5  ps-west.es.net (198.128.151.11)  24.696 ms !X  24.797 ms !X  24.791 ms !X

perfsonar-1850$

Hint #1: if I turn off IPv6, the problem goes away.

Hint #2: the system is connected to a router that sees only ESnet and I2 routes, with no default.

In any case, it seems that lsregistrationdaemon.pl shouldn't have that Perl error.

-- Pete