perfSONAR User Q&A and Other Discussion

[Antoine Delvaux <>]

Hi Edward,

Are you able to share with us the JSON file for your mesh?  We'll then be 
able to have closer look.

Thanks,

Antoine.

> Le 28 avr. 2017 à 08:17, Edward Toth 
> <>
>  a écrit :
> 
> Hello!
> 
> I recently updated my nodes to perfsonar 4.0, which mostly worked fine 
> (except for some hiccups).
> The setup contains a central management node and several test nodes in full 
> mesh configuration. A few days after the update I saw, that the central 
> archive is not getting any test results. The logs for pscheduler on the 
> test nodes and the management node do not show anything out of the ordinary.
> However I checked the meshconfig-guiagent log and saw that it is not able 
> to generate the configuration.
> 
> I copied the last entry (all entries look like this):
> 
> 2017/04/28 09:50:44 (15151) ERROR> GUIAgent.pm:219 
> perfSONAR_PS::MeshConfig::GUIAgent::__configure_guis - Problem generating 
> maddash configuration: Problem generating maddash configuration: Couldn't 
> find ma for host: perfSONAR_PS::MeshConfig::Config::Address=HASH(0x4c26070) 
> at 
> /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/MeshConfig/Generators/MaDDash.pm 
> line 352.
> 
> 
> The mesh configuration has not changed in almost a year, and it worked fine 
> before the update and for some time after the update to perfsonar 4.0.
> Searching the documentation I could not find anything either, except that 
> the perfsonar-meshconfig-guiagent replaces the generate_gui_configuration + 
> cronjob. Have I missed something?
> 
> I don't know either if this is related to the central archive not getting 
> results, or if this a different problem.
> 
> Thanks in advance for any help
> Edward Toth