perfSONAR User Q&A and Other Discussion

[Joe Breen <>]

Hi,

I was wondering if anyone had seen an error similar to the following?

##############

[chpcadmin@uofu-science-dmz-bandwidth ~]$ pscheduler task throughput --source uofu-ddc-dmz-latency.chpc.utah.edu
Submitting task...
Unable to determine the lead participant: At /schema: 1 is not one of [2]

##############

I am running the pscheduler command on 155.101.66.2 / uofu-science-dmz-bandwidth.chpc.utah.edu.

If I swap --source for --dest for the same address, I receive results.  If I explicitly put in the --dest and --source, I receive results:

############################

 [chpcadmin@uofu-science-dmz-bandwidth ~]$ pscheduler task throughput --source uofu-ddc-dmz-latency.chpc.utah.edu  --dest 155.101.66.2

Submitting task...
Task URL:
https://uofu-ddc-dmz-latency.chpc.utah.edu/pscheduler/tasks/6d955b5c-ef7d-4418-8717-34cfcca06ef0
Running with tool 'iperf3'
Fetching first run...

Next scheduled run:
https://uofu-ddc-dmz-latency.chpc.utah.edu/pscheduler/tasks/6d955b5c-ef7d-4418-8717-34cfcca06ef0/runs/a50bb22c-2b26-4b5d-ae3f-dd2f99320da6
Starts 2020-06-25T00:13:50Z (~6 seconds)
Ends   2020-06-25T00:14:09Z (~18 seconds)
Waiting for result...

* Stream ID 5
Interval       Throughput     Retransmits    Current Window
0.0 - 1.0      9.10 Gbps      22             2.16 MBytes    
1.0 - 2.0      9.11 Gbps      0              2.16 MBytes    
2.0 - 3.0      9.32 Gbps      1              1.22 MBytes    
3.0 - 4.0      9.32 Gbps      0              1.22 MBytes    
4.0 - 5.0      9.34 Gbps      2              1.56 MBytes    
5.0 - 6.0      9.32 Gbps      1              1.12 MBytes    
6.0 - 7.0      9.30 Gbps      0              1.17 MBytes    
7.0 - 8.0      9.21 Gbps      0              1.18 MBytes    
8.0 - 9.0      9.30 Gbps      0              1.25 MBytes    
9.0 - 10.0     9.30 Gbps      0              1.30 MBytes    

Summary
Interval       Throughput     Retransmits    
0.0 - 10.0     9.26 Gbps      26

No further runs scheduled.

##############################

The only Google hits for the specific error that we have turned up are:

https://github.com/perfsonar/pscheduler/issues/427

This github issue shows closed and fixed.  

Both my boxes are running 4.2.4 pscheduler

Any thoughts?

  --Joe