perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

Looks like the problem is that 64.251.58.166 is in a traceroute mesh but does not have a traceroute measurement_archive defined. You didn't see it pre-4.0 because the meshconfig-guiagent did not generate traceroute dashboards so it was ignoring those tests. 

That problem looks separate from the central archive not getting results. Looking at your pscheduler tasks on one of the hosts I could reach, it looks like they are having some type of problem reaching the archive. Running the command below shows an example of this if you are curious:

pscheduler result --archivings https://192.35.241.164/pscheduler/tasks/323d255d-c7de-47e5-81c6-d03e04926790/runs/c3cec40b-1d42-41e1-902f-c2e32635b288

From one of the hosts in question, are you able to run the following?

curl -k "http://128.130.2.80/esmond/perfsonar/archive/?limit=1"

If it gives a 500 error or similar, could you send me the logs under /var/log/esmond/ from the central archive host? It might be something is wrong with the archive. 

Thanks,

Andy

On April 28, 2017 at 6:39:03 AM, Edward Toth () wrote:

Hi,

thanks for the quick response! I attached the .json file to this email.
The schema of the json file should be OK, because it is generated from
.conf file.

Might be, that I overlooked some changes in the configuration?

Thanks,
Edward

On 2017-04-28 12:27, Antoine Delvaux wrote:
> 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

--

Technische Universität Wien http://www.tuwien.ac.at
ZID - Zentraler Informatikdienst/Kommunikation E020C
Wiedner Hauptstrasse 8-10/020, A-1040 Wien, Austria
Tel: +43 (1) 58801-420425