perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Cameron,

I think you can ignore those errors in web_admin.log. It sounds like maybe just a display issue with the services portion of that page since you stated you seem to still be getting scheduler test results and things like the lsregistrationdaemon are putting your host in the LS. Whether a service is displayed as “Running” or “not running” is by looking at it’s PID file(s) under /var/run and then checking the process with that PID to verify it has the expected process name. For example, perfsonar-lsregistrationdaemon should have a pid file under /var/run/lsregistrationdaemon.pid and the process it points at should have lsregistrationdaemon.pl in the name. Do both of those hold true on your machine? If not, what OS are you on?

Thanks,

Andy

On June 23, 2017 at 7:48:59 PM, Cameron Harr () wrote:

I recently updated my perfsonar node (v. 4.0.0.2-1) and services appear
to be working as well as scheduled tests; however, I can't get any of
the services in the dashboard to show anything but "Not Running."

I've looked at many log files and many don't have recent errors. The
ones that do are the user.log and the web_admin.log

In the user.log, I see many of the each of the following error message
interspersed with other normal messages.

Jun 23 13:09:00 beep powstream[5101]: getaddrinfo(): beep.ucllnl.org: Network is unreachable
Jun 23 13:10:26 beep powstream[69870]: getaddrinfo(): Name or service not known

In the web_admin log when I load the dashboard, I get the following
errors (as well as additional debug messages)

2017/06/23 13:09:38 (70054) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for peer_ports
2017/06/23 13:09:38 (70054) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for iperf_ports
2017/06/23 13:09:38 (70054) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for iperf3_ports
2017/06/23 13:09:38 (70054) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for nuttcp_ports
2017/06/23 13:09:38 (70054) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for thrulay_ports
2017/06/23 13:09:38 (70054) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for owamp_ports
2017/06/23 13:09:38 (70054) ERROR> BWCTL.pm:646 perfSONAR_PS::NPToolkit::Config::BWCTL::get_port_range - No port range for test_ports
2017/06/23 13:09:38 (70054) DEBUG> Host.pm:484 perfSONAR_PS::NPToolkit::DataService::Host::get_services - Checking owamp
...
2017/06/23 13:09:39 (70055) DEBUG> Utils.pm:119 perfSONAR_PS::Client::Utils::send_http_request - Sending HTTP GET to http://ps-west.es.net:8090/lookup/records/?host-name=192.12.137.251&type=host
2017/06/23 13:09:39 (70055) ERROR> Host.pm:329 perfSONAR_PS::NPToolkit::DataService::Host::get_details - Found host record in LS using 192.12.137.251

The port ranges it complains about are defined in
/etc/bwctl-server/bwctl-server.conf and the bwctl user has permissions
to read that file. Any ideas what else it might be?

Thanks,
Cameron