perfSONAR User Q&A and Other Discussion

[Michael Johnson <>]

To add on to what Ivan mentioned, you only have a local archive configured, 
even for mesh tests; this is one of your problems:

https://localhost/esmond/perfsonar/archive/

See:
https://perfsonar-1850.frgp.net/pscheduler/tasks/5721a884-a038-4cda-9cfb-e0c5f5d79134

Your archive should include the central MA for the quilt. In your 
/etc/perfsonar/meshconfig_agent.conf, do you have this set up?
configure_archives  1

You have other issues as well though, for instance when I try to run a 
latency test from your host to perfsonar.illinois.net, it works. In the other 
direction, I see this:
$ pscheduler task latency --dest perfsonar.illinois.net --source 
perfsonar-1850.frgp.net
Submitting task...
Task URL:
https://perfsonar-1850.frgp.net/pscheduler/tasks/7227ea2e-8eca-4cf2-83c4-4aebd69e2424
Running with tool 'owping'
Fetching first run...
perfsonar-1850.frgp.net never scheduled a run for the task.

I am not sure why pscheduler is not scheduling the run. I see this error, but 
I'm not sure what to make of it:

"iperf3 requires exactly 2 participants, got 1"

from here:
https://perfsonar-1850.frgp.net/pscheduler/tasks/5721a884-a038-4cda-9cfb-e0c5f5d79134/runs/2b7a1375-7229-46b6-ba4b-dfc8dc88de10

I hope this helps.

- Michael

On Mon, Aug 13, 2018 at 06:20:50PM -0600, Pete Siemsen wrote:
> Ever since I upgraded to 4.0.2, my (the FRGP's) participation in the Quilt
> mesh at http://quiltmesh.onenet.net/maddash-webui/ has been problematic. My
> whole row is orange. Embarrassing. I've appended the last 25 lines from
> /var/log/perfsonar/meshconfig-agent.log file. These messages mystify me
> because I can ping and/or traceroute to most of the hosts that appear in
> these error messages, like these
>
> ps-grand-bw.perfsonar.kanren.net
> kc-core-psr.mo.more.net
>
> perfsonar-1850$ tail --lines=25 meshconfig-agent.log
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(ps-svl-10g.cenic.net->perfsonar-1850.frgp.net),
> continuing with rest of config: 403 FORBIDDEN: Task forbidden by limits:
> Hints:
>  requester: 129.19.165.2
>  server: 137.164.28.121
> Identified as everybody
> Classified as default
> Application: Defaults applied to non-friendly hosts
>  Group 1: Limit 'innocuous-tests' failed: Test type not in list
>  Group 1: Want any, 0/1 passed, 1/1 failed: FAIL
>  Group 1: Failed; stopping here.
>  Application FAILS
> Proposal does not meet limits
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(ps-grand-bw.perfsonar.kanren.net->
> perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout:
> timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(ps-grand-lt.perfsonar.kanren.net->
> perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout:
> timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(nmon-aa.mich.net->perfsonar-1850.frgp.net),
> continuing with rest of config: 500 timeout: timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(kc-core-psr.mo.more.net->perfsonar-1850.frgp.net),
> continuing with rest of config: 500 timeout: timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(latency.eugn-perfsonar.nero.net->
> perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout:
> timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(bandwidth.eugn-perfsonar.nero.net->
> perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout:
> timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(perfsonar-1850.frgp.net->web100.pnw-gigapop.net),
> continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to
> determine participants: Process took too long to run.
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(web100.pnw-gigapop.net->perfsonar-1850.frgp.net),
> continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to
> determine participants: Process took too long to run.
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(perfsonar.unl.edu->perfsonar-1850.frgp.net),
> continuing with rest of config: 500 timeout: timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(perfsonar-msn.wiscnet.net->perfsonar-1850.frgp.net),
> continuing with rest of config: 500 timeout: timeout
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(perfsonar-1850.frgp.net->noctuidae.cns.vt.edu),
> continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to
> determine participants: Process took too long to run.
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(noctuidae.cns.vt.edu->perfsonar-1850.frgp.net),
> continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to
> determine participants: Process took too long to run.
> 2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: -
> Problem adding test trace(psonar.arc.vt.edu->perfsonar-1850.frgp.net),
> continuing with rest of config: 500 timeout: timeout
>
> Any clue appreciated :-)
>
> -- Pete

> --
> To unsubscribe from this list: 
> https://lists.internet2.edu/sympa/signoff/perfsonar-user


--
Michael Johnson
GlobalNOC DevOps Engineer

Attachment: smime.p7s
Description: S/MIME cryptographic signature