perfSONAR User Q&A and Other Discussion

[Johann Hugo <>]

Thanks, got it working now.

Another question:

New grids that I add to my pSconfig JSON file are visible in the json config file http://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json?format=psconfig, but not on my Maddash-webui.

psconfig-maddash-agent is running and the Maddash Agent is pointing to the JSON config file.

psconfig remote list

=== MaDDash Agent ===
[
   {
      "url" : "https://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json"
   }
]

What do I need to reload before the changes are visible in my Maddash-webui ?

https://perf-cm.sanren.ac.za/maddash-webui/

Regards

Johann

On Fri, May 31, 2019 at 5:06 PM Andrew Lake <> wrote:

Hi,

It looks like there was some confusion when you “psconfig remote add” got run on your measurement hosts. To get things to do what you want, run the following commands on your measurement hosts:

psconfig remote delete "https://perf-cm.sanren.ac.za/esmond/perfsonar/archive/“

psconfig remote add --configure-archives https://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json

If you run “psconfig remote list” after the above commands you should see something like the following:

[

   {

      "url" : "https://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json",

      "configure-archives" : true

   }

]

The first command above removes the pointer to the esmond URL. That URL is not a pointer to a pSconfig (or old meshconfig) JSON file, so it does not belong in there. The second command updates your pointer to sanren_mesh_2019.json to use the configure-archives option. That option means “for the JSON file referenced, use the archives defined in the file (if any)”, which is what you want.

Hope that helps,

Andy

On May 31, 2019 at 5:52:14 AM, Johann Hugo () wrote:

Hi

I'm trying to get a central measurement archive working for your perfSONAR deployment.

The network:

- PWA server to generate the pSConfig and MeshConfig json files

http://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json

- Central Management server running central archive + MaDDash agent + dashboard

esmond is configured to use IP based autherntication:

/usr/sbin/esmond_manage add_user_ip_address sanren 155.232.40.0/24 155.232.195.0/24 202 155.232.50.0/24

https://perf-cm.sanren.ac.za/esmond/perfsonar/archive/

https://perf-cm.sanren.ac.za/maddash-webui/

[root@perf-cm esmond]# psconfig remote list
=== MaDDash Agent ===
[
   {
      "url" : "http://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json"
   }
]

- Several measurement hosts, running the standard perfSONAR Toolkit ISO, configured to get remote pscheduler config file + use remote central archive.

[root@ps-1-pta-csir esmond]# psconfig remote list
=== pScheduler Agent ===
[
   {
      "url" : "https://perf-cm.sanren.ac.za/esmond/perfsonar/archive/",
      "configure-archives" : true
   },
   {
      "url" : "https://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json"
   }
]

Problem:

The measurement hosts only submits pScheduler test results to the local host, but never to the central archive.

tail -F /var/log/pscheduler/pscheduler.log
May 31 11:04:11 ps-1-pta-csir journal: runner INFO     643111: Posted result to https://ps-1-pta-csir-10g.perfsonar.ac.za/pscheduler/tasks/1437b0bf-f898-4f2b-b655-1177f59440a6/runs/4f58f1ae-7d56-4b08-85db-dd12fafa471

The psConfig file (sanren_mesh_2019.json) that all the measurements hosts use points to my central archive, but it looks like they never use it:

archives
config-archive0
archiver	"esmond"
data
url	"https://perf-cm.sanren.ac.za/esmond/perfsonar/archive/"
measurement-agent	"{% scheduled_by_address %}"

Any ideas how to debug this ?

Regards

Johann

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

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