perfSONAR User Q&A and Other Discussion

[Michael Johnson <>]

Hi Joel,

Thanks for those details. Are you running PWA v4.2.3?

It looks like this is a bug involving the "probe_type" field. It should not 
be displayed for throughput tests. I am opening a ticket on this issue.

If you want to fix it in the short term and you're familiar with mongodb, you 
can do something like this (backup your mongo db first, just in case)

$ mongo pwa

 db.testspecs.find({"name": "perf toolkit vers sonde"}).pretty();

There should be one result that has the parameters for your test. It will have one 
called "probe_type". If everything looks good, you can delete that field:

 db.testspecs.update({"name": "perf toolkit vers sonde"}, { $unset: 
{"specs.probe_type": ""}});

Otherwise you can wait for a fix.

Thanks,
Michael


On Tue, Mar 10, 2020 at 03:03:40PM +0000, Joël COSTAMAGNA wrote:
> Hello,
>
> I still have the same problem but I was able to narrow it down:
>
> I create a test in the psconfig web admin interface, but the request 
> in the toolkit pscheduler log have extra parameters, so the request 
> fail and the test is not started:
>
>
> here is the template published on the pwa host:
>
> {
>  "archives": {
>    "config-archive0": {
>      "archiver": "esmond",
>      "data": {
>        "url":"http://172.16.18.12/esmond/perfsonar/archive/";,
>        "measurement-agent": "{% scheduled_by_address %}"
>      }
>    }
>  },
>  "addresses": {
>    "172.16.18.13": {
>      "address": "172.16.18.13",
>      "host": "172.16.18.13",
>      "_meta": {
>        "display-name": "probe number one",
>        "display-url":"https://172.16.18.13/toolkit/";
>      }
>    },
>    "172.16.18.11": {
>      "address": "172.16.18.11",
>      "host": "172.16.18.11",
>      "_meta": {
>        "display-name": "main probe",
>        "display-url":"https://172.16.18.11/toolkit/";
>      }
>    },
>    "172.16.18.14": {
>      "address": "172.16.18.14",
>      "host": "172.16.18.14",
>      "_meta": {
>        "display-name": "probe number 2",
>        "display-url":"https://172.16.18.14/toolkit/";
>      }
>    }
>  },
>  "groups": {
>    "traceroute-all": {
>      "type": "mesh",
>      "addresses": [
>        {
>          "name": "172.16.18.13"
>        },
>        {
>          "name": "172.16.18.11"
>        },
>        {
>          "name": "172.16.18.14"
>        }
>      ]
>    },
>    "iperf toolkit vers sonde": {
>      "type": "mesh",
>      "addresses": [
>        {
>          "name": "172.16.18.13"
>        },
>        {
>          "name": "172.16.18.11"
>        },
>        {
>          "name": "172.16.18.14"
>        }
>      ]
>    },
>    "latency all": {
>      "type": "mesh",
>      "addresses": [
>        {
>          "name": "172.16.18.13"
>        },
>        {
>          "name": "172.16.18.11"
>        },
>        {
>          "name": "172.16.18.14"
>        }
>      ]
>    },
>    "ping": {
>      "type": "mesh",
>      "addresses": [
>        {
>          "name": "172.16.18.13"
>        },
>        {
>          "name": "172.16.18.11"
>        },
>        {
>          "name": "172.16.18.14"
>        }
>      ]
>    }
>  },
>  "tests": {
>    "traceroute-all": {
>      "type": "trace",
>      "spec": {
>        "source": "{% address[0] %}",
>        "dest": "{% address[1] %}",
>        "first-ttl": 1,
>        "wait": "PT1M",
>        "length": 1200
>      }
>    },
>    "iperf toolkit vers sonde": {
>      "type": "throughput",
>      "spec": {
>        "duration": "PT20S",
>        "source": "{% address[0] %}",
>        "dest": "{% address[1] %}",
>        "probe-type": "tcp",
>        "omit": "PT5S",
>        "ip-version": 4
>      }
>    },
>    "latency all": {
>      "type": "latencybg",
>      "spec": {
>        "source": "{% address[0] %}",
>        "dest": "{% address[1] %}",
>        "packet-interval": 0.1,
>        "bucket-width": 0.001,
>        "packet-count": 600,
>        "ip-version": 4
>      }
>    },
>    "ping": {
>      "type": "rtt",
>      "spec": {
>        "source": "{% address[0] %}",
>        "dest": "{% address[1] %}"
>      }
>    }
>  },
>  "schedules": {
>    "sched-0": {
>      "repeat": "PT10M",
>      "sliprand": true
>    },
>    "sched-1": {
>      "repeat": "PT4H",
>      "sliprand": true
>    },
>    "sched-2": {
>      "repeat": "PT1S",
>      "sliprand": true
>    }
>  },
>  "tasks": {
>    "traceroute-all": {
>      "group": "traceroute-all",
>      "test": "traceroute-all",
>      "archives": [
>        "config-archive0"
>      ],
>      "_meta": {
>        "display-name": "traceroute-all"
>      },
>      "schedule": "sched-0",
>      "tools": [
>        "bwctltraceroute",
>        "traceroute"
>      ]
>    },
>    "iperf toolkit vers sonde": {
>      "group": "iperf toolkit vers sonde",
>      "test": "iperf toolkit vers sonde",
>      "archives": [
>        "config-archive0"
>      ],
>      "_meta": {
>        "display-name": "iperf toolkit vers sonde"
>      },
>      "schedule": "sched-1",
>      "tools": [
>        "bwctliperf3",
>        "iperf3"
>      ]
>    },
>    "latency all": {
>      "group": "latency all",
>      "test": "latency all",
>      "archives": [
>        "config-archive0"
>      ],
>      "_meta": {
>        "display-name": "latency all"
>      },
>      "tools": [
>        "powstream"
>      ]
>    },
>    "ping": {
>      "group": "ping",
>      "test": "ping",
>      "archives": [
>        "config-archive0"
>      ],
>      "_meta": {
>        "display-name": "ping"
>      },
>      "schedule": "sched-2"
>    }
>  },
>  "_meta": {
>    "display-name": "test config"
>  },
>  "hosts": {
>    "172.16.18.13": {},
>    "172.16.18.11": {},
>    "172.16.18.14": {}
>  }
> }
>
>
>
>
> and in pscheduler.log on my toolkit I can see the request to pscheduler API:
>
> REQUEST: 
> GEThttps://localhost/pscheduler/tests/throughput/participants?spec={"source":"172.16.XXX.11
>
> ","dest":"172.16.XXX.13","probe-type":"tcp","duration":"PT20S","schema":1,"omit":"PT5S","ip-version":4}
>
> Mar 10 14:53:26 NTM-TLS-SVM-PFSTLKT journal: test-throughput/participants 
> DEBUG    Debug started
>
> Mar 10 14:53:26 NTM-TLS-SVM-PFSTLKT journal: pscheduler-api DEBUG    Response 
> 400: At /schema: 1 is not one of [2]
>
> If I manually remove the <<schema: 1>>and <<probe_type>> from the 
> request and open the URL in my browser, it returns the right json. I 
> do not see these parameters when I create the test in the web 
> interface, so I am not sure where it is added
>
>
>
>
> Regards ,
>
> joel costamagna
>
>
> Le 05/03/2020 à 10:56, Joël COSTAMAGNA a écrit :
> > hello,
> >
> > I am trying to use PWA to create my template, I used a central URL 
> > in the config tab, but when launching the tasks I have an error on 
> > my probe saying the archive template is 1 instead of 2
> >
> >
> > 2020/03/05 09:56:19 WARN pid=17933 
> > prog=perfSONAR_PS::PSConfig::PScheduler::Agent::_run_end line=227 
> > guid=888E9D8E-5EC7-11EA-86A6-F90A5A0DFF4A msg=Problem determining 
> > which pscheduler to submit test to for creation, skipping test 
> > throughput(172.16.XXX.11->172.16.XXX.13): BAD REQUEST: At /schema: 1 
> > is not one of [2]
> >
> > I see  on the archive documentation  that i can specify schema:2 in 
> > the archive config in my template, but I don't see where i can 
> > change this in the psconfig web interface
> >
> >
> > Regards,
> >
> > joel costamagna

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

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