perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Aaron,

Thanks, the agents file you sent looks good. Taking a second look at your JSON file though I see something I didn't notice before - it looks like maybe you just have one <host> defined and it has all the addresses. They each need to be in their own <host> object because I think right now the meshconfig-agent is skipping all the tests because it thinks it would just be a test to itself.

Thanks,

Andy 

On May 5, 2017 at 7:54:08 AM, C. Aaron Smith () wrote:

Hi again Andy,

Forgot to copy the list on my first reply. Thanks for taking a look.
Here is the /etc/perfsonar/meshconfig-agent.conf. There are manual
tests running on the test nodes to a set of nodes not part of the mesh
config. Those tests show up in the meshconfig-agent-tasks.conf file as
expected.

Thanks,
Aaron

On 5/4/2017 10:47 AM, Andrew Lake wrote:
> Hi Aaron,
>
> May seem like a silly question, but in your
> /etc/perfsonar/meshconfig-agent.conf are they pointing at
> http://128.91.196.207/mesh.json? If they are, could you send me
> /etc/perfsonar/meshconfig-agent.conf and I can double-check for anything
> else out of place. Looks like its just not reading that URL. It looks
> like what I assume are manual tests or tests from another mesh are
> getting created fine since if I go
> to https://165.123.50.178/pscheduler/tasks and dig down into one of the
> URLs its a new task, but looks like its running to a set of hosts not in
> the mesh shared.
>
> Thanks,
> Andy
>
>
> On May 4, 2017 at 10:07:58 AM, C. Aaron Smith (
> <mailto:>) wrote:
>
>> Hello all,
>>
>> I am setting up a mesh of test nodes as a proof of concept and running
>> into a problem. The testing nodes are not getting tests from the mesh.
>>
>> The test nodes are toolkit iso installs on centos 6, with perfsonar
>> upgraded to 4.0. The central mesh server is centos 7 toolkit iso
>> install of 4.0.
>>
>> The mesh configuration is derived from a conf file and can be found
>> here: http://128.91.196.207/mesh.json
>>
>> As per http://docs.perfsonar.net/multi_mesh_agent_config.html the test
>> nodes have /etc/perfsonar/meshconfig-agent.conf updated to use the above
>> file.
>>
>> /var/log/meshconfig-agent.log has updates like these:
>> 2017/05/03 10:37:01 (1107) INFO> perfsonar_meshconfig_agent:453 main:: -
>> Configuration file change detected, refreshing records.
>> 2017/05/03 10:39:32 (1107) INFO> perfsonar_meshconfig_agent:438 main:: -
>> Added 12 new tasks, and deleted 36 old tasks
>> 2017/05/03 10:51:32 (1107) INFO> perfsonar_meshconfig_agent:453 main:: -
>> Configuration file change detected, refreshing records.
>> 2017/05/03 10:52:18 (1107) INFO> perfsonar_meshconfig_agent:438 main:: -
>> Added 3 new tasks, and deleted 0 old tasks
>> 2017/05/04 03:53:51 (1107) INFO> perfsonar_meshconfig_agent:438 main:: -
>> Added 12 new tasks, and deleted 0 old tasks
>> 2017/05/04 04:52:19 (1107) INFO> perfsonar_meshconfig_agent:438 main:: -
>> Added 3 new tasks, and deleted 0 old tasks
>> 2017/05/04 09:19:54 (1107) INFO> perfsonar_meshconfig_agent:453 main:: -
>> Configuration file change detected, refreshing records.
>>
>> But the /etc/perfsonar/meshconfig-agent-tasks.conf on the test node is
>> not getting updated with the tasks from the mesh config.
>>
>> Where do I look on the test node to see if the mesh.json file is being
>> read by the test node?
>>
>> Thanks,
>> Aaron
>>
>> --
>> C. Aaron Smith
>> Senior Network Engineer
>> ISC Tech Services
>> University of Pennsylvania
>> OpenPGP Key ID: 0xC311AB25

--
C. Aaron Smith
Senior Network Engineer
ISC Tech Services
University of Pennsylvania
OpenPGP Key ID: 0xC311AB25