perfSONAR User Q&A and Other Discussion

[Cameron Harr <>]

Ivan,

Thanks for the information. The pscheduler services were all running and 
the immediate issue in the GUI was due to read permissions on the .pid 
files.

FWIW, I have no need for backwards compatibility but didn't see any 
special documentation on migration other than noting the move from bwctl 
to pscheduler here: http://docs.perfsonar.net/pscheduler_intro.html. If 
there are other steps I need to do, please let me know where I can read 
up on them.

Thanks again,

Cameron

On 06/26/2017 02:15 AM, Garnizov, Ivan (RRZE) wrote:
> Hi Cameron,
>
> You are referring here to multiple issues.
> I would suggest opening different email conversations, since different people 
> may be involved and also in time it might get messy with respect to the 
> different services.
>
> In your email you are referring  to (sharing concerns wrt) the old model of 
> operation of perfSONAR on the coordination of measurements, while you have 
> installed 4.0.0.2-1. With the pS 4.0 release you should be looking for 
> pscheduler service and issues related, unless you have decided to stick with 
> old backwards compatibility stuff.
>
> Please check your for events on the new pS test coordination in 
> /var/log/pscheduler/pscheduler.log and the status of the  
> pscheduler-archiver, pscheduler-runner, pscheduler-scheduler and  
> pscheduler-ticker services.
>
> Regards,
> Ivan
>
>
> -----Original Message-----
> From: 
>
>  
> [mailto:]
>  On Behalf Of Cameron Harr
> Sent: Samstag, 24. Juni 2017 01:48
> To: 
>
> Subject: [perfsonar-user] perfsonar dashboard services all show Not Running
>
> 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