Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts


Chronological Thread 
  • From: matt fetting <>
  • To: Szymon Trocha <>
  • Cc:
  • Subject: Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts
  • Date: Fri, 26 Jan 2018 10:09:52 -0500
  • Ironport-phdr: 9a23:mYzJEhxa7is4VkfXCy+O+j09IxM/srCxBDY+r6Qd2+MSIJqq85mqBkHD//Il1AaPAd2Craocw8Pt8InYEVQa5piAtH1QOLdtbDQizfssogo7HcSeAlf6JvO5JwYzHcBFSUM3tyrjaRsdF8nxfUDdrWOv5jAOBBr/KRB1JuPoEYLOksi7ze+/94HObwlSmDaxfa55IQmrownWqsQYm5ZpJLwryhvOrHtIeuBWyn1tKFmOgRvy5dq+8YB6/ShItP0v68BPUaPhf6QlVrNYFygpM3o05MLwqxbOSxaE62YGXWUXlhpIBBXF7A3/U5zsvCb2qvZx1S+HNsDtU7s6RSqt4LtqSB/wiScIKTg58H3MisdtiK5XuQ+tqwBjz4LRZoyeKfhwcb7Hfd4CR2VBUMZfWSJCDI2hcYUAE/EMMvxEo4TnvVYCsQeyCAuqCejyyjFInHj23agi3uQkCw7GwBAgFM8AsHvKsNX1KKYSUea6zKLVyjjDaulZ2Svh6ITSfBAuv+2MXa5xccrXxkkiDAzFjlCKpozkOzOZzPgCs2+e7+d5U++klmApqwZ0oje1x8csjJHEhpoLxVDe+yV524E1JduiR05he9KkFoVftz2CO4tuXswiWHpotDwiyr0Cv5OwYSsEyIw/yhLBcfOLb5SE7xf+WOueITp0mHdodb2jixqv7UStz/HzWtW23VtPqydJjNfBu38L2hfO8MaIUOF98V2k2TuX1wDc9OVEIUcsmKreMZEhw7owmoMXsUTNAiP6gUr3gLGYe0gr4OSo5OPnYrLppp+YKYB4kB3xMqMrmsCnAOQ4NBYBX3SD9OiizrLv4VH1TbBXgvA5kqTVrJXXKMsHqqKkHwNY15os5wq9Ajqj1dkUg3cKIV1ddBKClYfpOlXOIP7iDfe4hlShiDJryOraPr39GJnNIGbMkKv9fbZ87U5cxxE+zd9a551OC7EBJOj/VVP2tNzdFhM5KRC7w/77CNVh0YMTQXqPDbGDMKPcql+I4eQvLPOWZIMMpTb9MOYq5+T1gH89mF8dZrWp3YAJZHyiH/RmJVmZbmT2gtcHD2gKohQyQPb0h1KfTD4AL0q1Cpku9zQ8DsqaF4DIRonl1KeTzSK8GNtKfGdNClmkFH7uMZ2DSfEFbmSKJpkyvCYDUO2kQpM9nR+jqBP7zbUveu/d5jFeu5//yNlz6MXckBgz8Xp/CMHLgDLFdH19gm5dH2x+56t4u0Eojw7biaU=

Clarifying to make sure I am using the right terminology, I have one MA and two testing hosts. The two testing hosts are using API authentication and not IP authentication, and I created the API user on the MA box. 

When I visit the MA host on /esmond/perfsonar/archive or /esmond/perfsonar/archive/?format=json, I get information that I would expect to see based on my limited understanding: tests and IPs based on my published mesh config. 

David mentioned doing some pscheduler service level debug. Not sure which services to plug in here. Since the logs aren't helping me at the moment, I'm interested in turning up debugging or seeing where the failure is occurring. Based on the problem (MaDDash: Unable to find any tests with data in the given time range where source is host1 and destination is host2), how do I enable more debug or logging to see whats going on? Totally unsure of where to turn my attention at the moment!

Thanks for the continued support

On Fri, Jan 26, 2018 at 8:59 AM, Szymon Trocha <> wrote:
Hi Matt,

W dniu 25.01.2018 o 23:06, matt fetting pisze:
"pscheduler schedule +PT1H" does show all of the pending tests I would expect to see.

I am running a tail -f /var/log/perfsonar/* so I can see all logs, and have nothing new that's really jumping out since the reboot of the two nodes this morning. However, still don't have data in MaDDash. FWIW, I generated by MaDDash YAML from the central mesh config I am publishing from my MA, which is non participatory.

Maddash is trying to get data from the central MA run at http://YOUR_MA_HOST/esmond/perfsonar/archive/. That is populated by periodically polling the MAs running locally on each of your machines and copying the results to central.

What happens if you access http://YOUR_MA_HOST/esmond/perfsonar/archive/?format=json
This should return some contect if the data is there

Did you configure authentication (e.g. by IP) at central host along the lines in http://docs.perfsonar.net/multi_ma_install.html#authenticating-measurement-hosts ?

regards,

--
Szymon Trocha

Poznań Supercomputing & Networking Center
Tel. +48 618582022 ::: http://noc.pcss.pl





Archive powered by MHonArc 2.6.19.

Top of Page