perfSONAR User Q&A and Other Discussion

[David Szydloski <>]

I have a dozen or so nodes running tests as part of a mesh configuration. Now I need to add some non-mesh tests specifically rtt tests to some Anycast addresses. I have no problem running the tests themselves via the command line:

dszydloski@netperf01-ewr1:/var/log/pscheduler$ clear; sudo pscheduler task --debug rtt --dest 159.117.206.64

sudo: unable to resolve host netperf01-ewr1

2018-03-13T20:06:14 Debug signal ignored; already not debugging

2018-03-13T20:06:14 Debug discontinued

2018-03-13T20:06:14 Assistance is from localhost

2018-03-13T20:06:14 Forcing default slip of PT5M

2018-03-13T20:06:14 Converting to spec via https://localhost/pscheduler/tests/rtt/spec

Submitting task...

2018-03-13T20:06:14 Fetching participant list

2018-03-13T20:06:14 Spec is: {"dest": "159.117.206.64", "schema": 1}

2018-03-13T20:06:14 Params are: {'spec': '{"dest": "159.117.206.64", "schema": 1}'}

2018-03-13T20:06:15 Got participants: {u'participants': [None], u'null-reason': u'No source specified'}

2018-03-13T20:06:15 Lead is None

2018-03-13T20:06:15 Null reason is No source specified

2018-03-13T20:06:15 Pinging https://netperf01-ewr1/pscheduler/

2018-03-13T20:06:15 Pinging https://localhost/pscheduler/

2018-03-13T20:06:15 localhost is up

2018-03-13T20:06:15 Posting task to https://localhost/pscheduler/tasks

2018-03-13T20:06:15 Data is {"test": {"type": "rtt", "spec": {"dest": "159.117.206.64", "schema": 1}}, "schema": 1, "schedule": {"slip": "PT5M"}}

Task URL:

https://localhost/pscheduler/tasks/3748728a-5c15-4fd6-8a59-3422dd54be88

2018-03-13T20:06:17 Posted https://localhost/pscheduler/tasks/3748728a-5c15-4fd6-8a59-3422dd54be88

Running with tool 'ping'

Fetching first run...

2018-03-13T20:06:17 Fetching https://localhost/pscheduler/tasks/3748728a-5c15-4fd6-8a59-3422dd54be88/runs/first

2018-03-13T20:06:18 Handing off: pscheduler watch --format text/plain --debug https://localhost/pscheduler/tasks/3748728a-5c15-4fd6-8a59-3422dd54be88

2018-03-13T20:06:18 Debug signal ignored; already not debugging

2018-03-13T20:06:18 Debug discontinued

2018-03-13T20:06:18 Fetching https://localhost/pscheduler/tasks/3748728a-5c15-4fd6-8a59-3422dd54be88

Next scheduled run:

https://localhost/pscheduler/tasks/3748728a-5c15-4fd6-8a59-3422dd54be88/runs/c909ca97-9092-4d73-9081-1212cac7b77c

Starts 2018-03-13T20:06:27Z (~8 seconds)

Ends 2018-03-13T20:06:38Z (~10 seconds)

Waiting for result...

1 159.117.206.64 64 Bytes TTL 63 RTT 0.6650 ms

2 159.117.206.64 64 Bytes TTL 63 RTT 0.5520 ms

3 159.117.206.64 64 Bytes TTL 63 RTT 0.6970 ms

4 159.117.206.64 64 Bytes TTL 63 RTT 0.5570 ms

5 159.117.206.64 64 Bytes TTL 63 RTT 0.5520 ms

0% Packet Loss RTT Min/Mean/Max/StdDev = 0.552000/0.604000/0.697000/0.068000 ms

I've manually appended it to the /etc/perfsonar/meshconfig-agent-tasks.conf file like this:

<test>

    <schedule>

        type   regular_intervals

        interval   1200

    </schedule>

    target   159.117.207.64

    target   159.117.206.64

    local_interface   ens3

    <parameters>

        type   bwping

        send_only   1

        test_ipv4_ipv6   1

    </parameters>

    description   Anycast RTT Testing

</test>

However, the meshconfig-agent having some issues scheduling the jobs:

dszydloski@netperf01-ewr1:~$ tail /var/log/perfsonar/meshconfig-agent.log

2018/03/13 20:46:23 (15589) ERROR> perfsonar_meshconfig_agent:420 main:: - Error building pScheduler task: Not implemented. Must be overridden by subclass. at /usr/share/perl5/perfSONAR_PS/RegularTesting/Tests/BwctlBase.pm line 602.

2018/03/13 20:49:46 (15589) INFO> perfsonar_meshconfig_agent:453 main:: - Configuration file change detected, refreshing records.

2018/03/13 20:50:09 (15589) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test rtt(159.117.198.155->159.117.207.64): 400 BAD REQUEST: Neither the source nor destination is running pScheduler.

2018/03/13 20:50:09 (15589) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test rtt(159.117.207.64->159.117.198.155): 400 BAD REQUEST: Neither the source nor destination is running pScheduler.

2018/03/13 20:50:09 (15589) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test rtt(159.117.198.155->159.117.206.64): 400 BAD REQUEST: Neither the source nor destination is running pScheduler.

2018/03/13 20:50:09 (15589) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test rtt(159.117.206.64->159.117.198.155): 400 BAD REQUEST: Neither the source nor destination is running pScheduler.

Has anyone ran into similar issues before? I'm able to run bwping / rtt tests to other hosts in the mesh without issue.

Thanks for your help,

--

David Szydloski

Core Deployment Engineer

VidScale, Inc.