perfSONAR User Q&A and Other Discussion

[Zhi-Wei Lu <>]

Thank you, Mark!

curl gets nothing from pb -> p0, I was able to get output from other servers from pb. For example  between pb -> p5

"This is the pScheduler API server on p5.noc.ucdavis.edu (mammoth-v4.noc.ucdavis.edu)."

During the curl run, there are packet exchanges between pb<->p0, but there was no output on the command line, stuck there.

This problem started on Nov. 29, 2018, there were perfsonar updates on Nove 27 on all our servers (automatic update).

Currently,  between some of our servers, your "curl" commands work, but others fail.  

It appears to me, the update broke my setup, but I don't know what I need to change to accommodate those updates.

Thank you.

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

---

From: Mark Feit <>
Sent: Tuesday, January 8, 2019 6:02:13 AM
To: Zhi-Wei Lu;
Subject: Re: [perfsonar-user] RE: limits.conf file

 

Zhi-Wei Lu writes:

 

On my host pb.noc.ucdavis.edu, I can run rtt to p0.noc.ucdavis.edu, but not throughput.

 

Throughput is one of a few tests that require two pSchedulers (we call them “participants”) to work together to find a time when the test can be run.  The communication between them happens via pScheduler’s REST API, which uses HTTPS, so if that’s blocked, nothing is going to work.  The troubleshooter’s “checking for pScheduler” is the equivalent of “pscheduler ping HOSTNAME,” which attempts to fetch the API’s root resource.  ( You can try that yourself with “curl -Lk https://HOSTNAME/pscheduler”.)

 

All of the other tests (RTT, trace, idle, etc.) are single-participant, which means the machine where it runs is the only one involved and pScheduler doesn’t have to do anything off-host.

 

--Mark