perfSONAR User Q&A and Other Discussion

[Sowmya Balasubramanian <>]

H John,

I am checking with our infrastructure team here at ESnet to see if it is an issue on our side. I will let you know as soon as I hear from them.

Thanks,

Sowmya

On Mon, Jan 4, 2016 at 12:39 PM, John Bell <> wrote:

Hello,

I have configured a new perfsonar installation for a remote site, using the CentOS 6 ISO from perfsonar’s website. 

Immediately after installation, I went into the https://server/toolkit url, but it continues to show “Loading…” for endless amounts of time.

In /var/log/perfsonar/web_admin/web_admin.log, I find the following errors:

[root@ps-hssb-1 web_admin]# cat web_admin.log | grep 2016

2016/01/04 13:24:47 (22444) ERROR> BWCTL.pm:847 perfSONAR_PS::NPToolkit::Config::BWCTL::reset_state - BWCTL_CONF: $VAR1 = {

2016/01/04 13:24:47 (22444) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for iperf3_ports

2016/01/04 13:24:47 (22444) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for thrulay_ports

2016/01/04 13:24:47 (22444) DEBUG> Host.pm:414 perfSONAR_PS::NPToolkit::DataService::Host::get_services - Checking owamp

2016/01/04 13:24:47 (22443) DEBUG> Host.pm:298 perfSONAR_PS::Utils::Host::discover_primary_address - 129.24.23.235 is ipv4

2016/01/04 13:24:47 (22443) DEBUG> Host.pm:359 perfSONAR_PS::Utils::Host::discover_primary_address - 129.24.23.235 is IPv4

2016/01/04 13:24:47 (22443) DEBUG> Host.pm:361 perfSONAR_PS::Utils::Host::discover_primary_address - 129.24.23.235 isn't private or we're okay with private addresses

2016/01/04 13:24:47 (22443) DEBUG> Host.pm:410 perfSONAR_PS::Utils::Host::discover_primary_address - Selected em1/129.24.23.235 as the primary address

2016/01/04 13:24:47 (22443) DEBUG> Host.pm:417 perfSONAR_PS::Utils::Host::discover_primary_address - Selected em1/129.24.23.235 as the primary ipv4 address

2016/01/04 13:24:47 (22443) DEBUG> Host.pm:428 perfSONAR_PS::Utils::Host::discover_primary_address - No primary ipv6 address found

2016/01/04 13:24:47 (22443) ERROR> LookupService.pm:73 perfSONAR_PS::Utils::LookupService::discover_lookup_services - Problem retrieving http://ps1.es.net:8096/lookup/activehosts.json: 500 Can't connect to ps1.es.net:8096 (connect: Permission denied)

2016/01/04 13:24:47 (22443) ERROR> LookupService.pm:121 perfSONAR_PS::Utils::LookupService::is_host_registered - Unable to determine ls_url

2016/01/04 13:24:47 (22443) ERROR> Host.pm:246 perfSONAR_PS::NPToolkit::DataService::Host::get_details - Unable to find host record in LS using 129.24.23.235

2016/01/04 13:24:47 (22443) ERROR> LookupService.pm:73 perfSONAR_PS::Utils::LookupService::discover_lookup_services - Problem retrieving http://ps1.es.net:8096/lookup/activehosts.json: 500 Can't connect to ps1.es.net:8096 (connect: Permission denied)

2016/01/04 13:24:47 (22443) ERROR> LookupService.pm:121 perfSONAR_PS::Utils::LookupService::is_host_registered - Unable to determine ls_url

2016/01/04 13:24:47 (22443) ERROR> Host.pm:265 perfSONAR_PS::NPToolkit::DataService::Host::get_details - Unable to find host record in LS using hostname ps-hssb-1

It seems that the daemon is having issues using connect(), and I am assuming that this is why I cannot load the web interface. When I look at running services, I find that ls_registration_daemon.pl is running as the user perfsonar.

Where do I allow the perfsonar shell account access to use connect()?

Thank you for the assistance,

-- John Bell

IT Networks

University of New Mexico