perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

On February 21, 2017 at 4:09:57 AM, Daniel Spisak () wrote:

On Feb 21, 2017 12:47 AM, "Szymon Trocha" <> wrote:

Hi Daniel,

W dniu 20.02.2017 o 23:24, Daniel Spisak pisze:           

Moving onto MadDash, I was able to get that to load on my test setup, but it had a config that I had not created in it and it wasnt working. Looking at the error message for maddash it offered a number of things to verify. One of these was 

"Verify that /usr/lib/perfsonar/bin/generate_gui_configuration has run recently and you are looking at an accurate test mesh"

Except this binary does not exist at all on my centralmanagement server. What is this called now?

Are you saying this file don't exist in your server where you installed maddash? I'm not sure what your setup is and what you insatlled where.

Regards,

--  
Szymon Trocha

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

Yes, that is exactly what I am saying. The binary doesn't exist there. I didn't install maddash, this was done for me by installing the centralmanagement RPM bundle for perfsonar 4.0rc3 and I'm trying to figure out what the new equivalent is.

In 4.0 that script has become a daemon called perfsonar-meshconfig-guiagent. If you want to force an immediate update you can run “systemctl restart perfsonar-meshconfig-guiagent” on CentOS 7 and on CentOS 6 you can do "/sbin/service perfsonar-meshconfig-guiagent restart", otherwise it will update within a minute of you making a change to /etc/perfsonar/meshconfig-guiagent.conf and pulls down any changes to the remote JSON files within an hour by default.