perfSONAR User Q&A and Other Discussion

[Zhi-Wei Lu <>]

Thanks, Mark!

 

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

 

pscheduler task rtt --source pb.noc.ucdavis.edu --dest p0.noc.ucdavis.edu

Submitting task...

Task URL:

https://pb.noc.ucdavis.edu/pscheduler/tasks/abe061d1-f34e-4bbf-8df1-35bf07d50c2b

Running with tool 'ping'

Fetching first run...

 

Next scheduled run:

https://pb.noc.ucdavis.edu/pscheduler/tasks/abe061d1-f34e-4bbf-8df1-35bf07d50c2b/runs/1de5a810-2503-4ef2-bdcf-9baf1d535498

Starts 2019-01-07T22:32:24Z (~7 seconds)

Ends   2019-01-07T22:32:35Z (~10 seconds)

Waiting for result...

 

1       grx-v4.noc.ucdavis.edu (128.120.242.118)  64 Bytes  TTL 62  RTT   0.6000 ms

2       grx-v4.noc.ucdavis.edu (128.120.242.118)  64 Bytes  TTL 62  RTT   0.4120 ms

3       grx-v4.noc.ucdavis.edu (128.120.242.118)  64 Bytes  TTL 62  RTT   0.3650 ms

4       grx-v4.noc.ucdavis.edu (128.120.242.118)  64 Bytes  TTL 62  RTT   0.3590 ms

5       grx-v4.noc.ucdavis.edu (128.120.242.118)  64 Bytes  TTL 62  RTT   0.3550 ms

 

0% Packet Loss  RTT Min/Mean/Max/StdDev = 0.355000/0.418000/0.600000/0.094000 ms

 

No further runs scheduled.

 

But, throughtput test fails:

pscheduler task throughput --source pb.noc.ucdavis.edu --dest p0.noc.ucdavis.edu

Submitting task...

Unable to post task: Error getting tools from p0.noc.ucdavis.edu: Request timed out

The 'pscheduler troubleshoot' command may be of use in problem

diagnosis. 'pscheduler troubleshoot --help' for more information.

 

pscheduler troubleshoot p0.noc.ucdavis.edu

Performing basic troubleshooting of localhost and p0.noc.ucdavis.edu.

 

localhost:

 

  Checking path MTU... Unsafe or unknown: Found only one MTU in trace to localhost

  Checking for pScheduler... OK.

  Checking clock... OK.

  Idle test.... 9 seconds.... Checking archiving... OK.

 

p0.noc.ucdavis.edu:

 

  Checking path MTU... Unsafe or unknown: Error: Process took too long to run.

  Checking for pScheduler... Failed.

Request timed out

 

But, I am puzzled that “rtt” works with pscheduler on p0 from pb.

 

From: Mark Feit <>
Sent: Monday, January 07, 2019 12:21 PM
To: Zhi-Wei Lu <>;
Subject: Re: [perfsonar-user] RE: limits.conf file

 

 

On pb.noc.ucdavis.edu, I had problem to talk to pscheduler on p0.noc.ucdavis.edu

 …

  Checking path MTU... Unsafe or unknown: Error: Process took too long to run.

  Checking for pScheduler... Failed.

Request timed out

 

I wonder what it prevents pscheduler to talk to p0.noc.ucdavis.edu from pb.noc.ucdavis.edu.

 

I was able to reach pScheduler on both hosts from outside of UC Davis and ran some tests between them.  pScheduler is working fine on both and ICMP echo traffic and the UDP packets to make traceroute function work in both directions.  HTTPS traffic, which is how pSchedulers communicate with each other, does not, suggesting that something in the network between them is blocking it.