perfSONAR User Q&A and Other Discussion

[Szymon Trocha <>]

Just for record that I replied to Renan asking to uncomment <mesh> tags.
I just got confirmation it helped

Szymon

W dniu 05.06.2018 o 11:51, Renan PHILIPPE pisze:

Hi all,

I'm trying to add a new probe in my mesh configuration but it's not working, new proble seems to not download it confgiuration from maddash server.

So first, on Maddash server, new probe(IP 193.49.159.176) has been added to the meshconfiguration(you can see it on https://194.57.4.31/confmesh.json).

Secondary, on the new probe, I have configured the file /etc/perfsonar/meshconfig-agent.conf pointing on my Maddash server:

#<mesh>
#    ## Use 'configuration_url' to specify the URL where the agent should obtain
#    ## the mesh configuration from
     configuration_url             https://194.57.4.31/confmesh.json
#
#    ## To ensure that the configuration is trusted, you can set the

At first, I was thinking a Firewall problem but seems to be fine.

On new probe, I'm able to contact Maddash server, I tester the connectivity on https doing a "[root@bordeaux-pv-c7-Perf-01 PerfSonar1]# curl -vk https://194.57.4.31/confmesh.json".

When I execute this command on my new probe, I'm able to see the json configuration.

Tell me if I'm right but this test confirm that there's no connectivity issue?

On probe, I tried to force the probe to contact Maddash and dowload configuration executing the command "systemctl restart perfsonar-meshconfig-agent"

But seems not working because /etc/perfsonar/meshconfig-agent-tasks.conf  has not the configuration JSON.

On log meshconfig-agent.log, I don't see any line with the IP of the Maddash server, should I have one indicating that probe try to reach MAddash Server?

Thanks a lot for your help,

Renan.

Renan PHILIPPE
GIP RENATER | 23-25 rue Daviel | 75013 Paris
Tel: +33 1 53 94 20 66 / +33 6 24 50 32 28
Mail:
http://www.renater.fr

-- 
Szymon Trocha

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