perfsonar-user - Re: [perfsonar-user] Throughput job not being scheduled - BAD REQUEST: At /schema: 1 is not one of [2]
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] Throughput job not being scheduled - BAD REQUEST: At /schema: 1 is not one of [2]
Chronological Thread
- From: Mark Feit <>
- To: "Whitworth, Luke" <>, "" <>
- Subject: Re: [perfsonar-user] Throughput job not being scheduled - BAD REQUEST: At /schema: 1 is not one of [2]
- Date: Thu, 9 Jul 2020 16:20:52 +0000
Whitworth, Luke writes:
2020/07/09 16:17:19 WARN pid=1296 prog=perfSONAR_PS::PSConfig::PScheduler::Agent::_run_end line=227 guid=628dae27-076e-45b1-8352-1df84b897a76 msg=Problem determining which pscheduler to submit test to for creation, skipping test throughput(xxx.ac.uk->xxx.ac.uk): BAD REQUEST: At /schema: 1 is not one of [2]
The spec for test_throughput contains a bogus “tcp-bandwidth” parameter; you probably want “bandwidth.”
Tip: If you’re generating the JSON by hand, the names of the parameters match the command-line interface’s switches (see “pscheduler task throughput –help”, for example). You can also produce the JSON from the command line with “pscheduler task --export throughput --dest foo –bandwidth 1G | jq .test”.
The awfulness of the error message was brought to our attention a couple of months ago (see https://lists.internet2.edu/sympa/arc/perfsonar-developer/2020-04/msg00004.html). Improvements to that have been made and will be shipped in 4.3.0.
--Mark
|
- [perfsonar-user] Throughput job not being scheduled - BAD REQUEST: At /schema: 1 is not one of [2], Whitworth, Luke, 07/09/2020
- <Possible follow-up(s)>
- Re: [perfsonar-user] Throughput job not being scheduled - BAD REQUEST: At /schema: 1 is not one of [2], Mark Feit, 07/09/2020
- Re: [perfsonar-user] Throughput job not being scheduled - BAD REQUEST: At /schema: 1 is not one of [2], Whitworth, Luke, 07/09/2020
Archive powered by MHonArc 2.6.19.