perfSONAR User Q&A and Other Discussion

[John Simpkins <>]

Thanks for the help, as always. I'm still getting the limit failure:

2016/10/19 14:42:07 (3062) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 403 FORBIDDEN: Task forbidden by limits:

Identified as everybody

Classified as everybody, default

Application: Defaults

    Group 1: Limit 'innocuous-tests' failed: Test type not in list

    Group 1: Limit 'rtt-default' failed: Test is not 'rtt'

    Group 1: Limit 'throughput-default' failed: Test is not 'throughput'

    Group 1: Want any, 0/3 passed, 3/3 failed: FAIL

    Group 1: Failed; stopping here.

    Application FAILS

Proposal does not meet limits

And here's what that innocuous-tests block looks like on this host:

{

            "name": "innocuous-tests",

            "description": "Tests that are harmless",

            "type": "test-type",

            "data": {

                "types": [

                "latency",

                "rtt",

                "simplestream",

                "trace"

                ]

                }

        },

On Tue, Oct 18, 2016 at 1:55 PM Mark Feit <> wrote:

(Sorry for the late reply; the draft got buried.)

 

John Simpkins writes:

 

I'm seeing similar, but not quite the same, results.

 

2016/10/11 16:17:10 (3243) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine duration of test: Traceback (most recent call last):

  File "/usr/libexec/pscheduler/commands/../classes/tool/bwctliperf3/duration", line 26, in <module>

    duration += int(json['omit'])

ValueError: invalid literal for int() with base 10: 'PT10S'

...

2016/10/11 16:17:10 (3243) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 403 FORBIDDEN: Task forbidden by limits:

Identified as everybody

Classified as everybody, default

Application: Defaults

    Group 1: Limit 'innocuous-tests' failed: Test type not in list

    Group 1: Limit 'rtt-default' failed: Test is not 'rtt'

    Group 1: Limit 'throughput-default' failed: Test is not 'throughput'

    Group 1: Want any, 0/3 passed, 3/3 failed: FAIL

    Group 1: Failed; stopping here.

    Application FAILS

Proposal does not meet limits

 

 

The limit failure is the result of a mistake on my part where a couple of the innocuous tests didn’t get put into the list used in the limit configuration we shipped with RC1.  The file we ship in RC2 will be fixed.

 

As a stopgap, you can edit /etc/pscheduler/limits.conf, locate the “innocuous-tests” section, add “rtt” to the list list of test types and restart httpd.

 

--Mark