perfsonar-user - Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2]
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2]
Chronological Thread
- From: Chris Konger - NOAA Affiliate <>
- To:
- Subject: Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2]
- Date: Thu, 25 Jun 2020 03:09:11 -0600
I have seen that error previously ... for us we changed the "schema" line to value "3" and the problem went away. I looked up the json schema standards and couldn't make sense of what the differences were, but that made it go away for our tests. :) Chris Konger
Sr Network Engineer - Cloud (Contractor) NOAA Mail stop: N-Wave 325 Broadway Boulder, CO 80305 Phone: 303-497-7125 Cell: 720.650.9801 On 6/24/20 6:47 PM, Curtis, Bruce
wrote:
No answers but I see the same results on our perfsonar server. [curtis@perfsonar2 ~]$ 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] [curtis@perfsonar2 ~]$ I never noticed before, I guess I’ve always used both source and dest. [curtis@perfsonar2 ~]$ pscheduler task throughput --source uofu-ddc-dmz-latency.chpc.utah.edu --dest perfsonar2.it.ndsu.edu Submitting task... Task URL: https://uofu-ddc-dmz-latency.chpc.utah.edu/pscheduler/tasks/06299597-f275-4e8a-ba6a-92cce924af1c Running with tool 'iperf3' Fetching first run... Next scheduled run: https://uofu-ddc-dmz-latency.chpc.utah.edu/pscheduler/tasks/06299597-f275-4e8a-ba6a-92cce924af1c/runs/f1633cbd-9414-47fa-ae5b-357ff6dbb7e7 Starts 2020-06-25T00:43:38Z (~193 seconds) Ends 2020-06-25T00:43:57Z (~18 seconds) Waiting for result... * Stream ID 5 Interval Throughput Retransmits Current Window 0.0 - 1.0 3.15 Gbps 230 23.15 MBytes 1.0 - 2.0 5.20 Gbps 0 23.15 MBytes 2.0 - 3.0 5.20 Gbps 0 23.15 MBytes 3.0 - 4.0 5.20 Gbps 0 23.15 MBytes 4.0 - 5.0 5.20 Gbps 0 23.15 MBytes 5.0 - 6.0 5.20 Gbps 0 23.15 MBytes 6.0 - 7.0 5.17 Gbps 0 23.15 MBytes 7.0 - 8.0 5.17 Gbps 0 23.15 MBytes 8.0 - 9.0 5.21 Gbps 0 23.15 MBytes 9.0 - 10.0 5.21 Gbps 0 23.15 MBytes Summary Interval Throughput Retransmits 0.0 - 10.0 4.99 Gbps 230 No further runs scheduled. On Jun 24, 2020, at 7:27 PM, Joe Breen wrote: 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 -- To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user Bruce Curtis Network Engineer / Information Technology NORTH DAKOTA STATE UNIVERSITY phone: 701.231.8527 -- To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user |
- [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2], Joe Breen, 06/25/2020
- Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2], Curtis, Bruce, 06/25/2020
- Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2], Chris Konger - NOAA Affiliate, 06/25/2020
- Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2], Mark Feit, 06/25/2020
- Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2], Curtis, Bruce, 06/25/2020
Archive powered by MHonArc 2.6.19.