perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

The first error "Multiple 'host’ elements associated with the addresses on this machine” is as you said because you have multiple host definitions that match the host on your machine. They need to be merged for the mesh-config to build the tests. Let me know if you need help doing that. FWIW it is not a new requirement, 3.5 threw the same error. 

The second error, "Can't call method “bind_maps…”, may just be a byproduct of the first. Someone else saw the same thing in the past couple weeks and also had the first error. The fact that the error message displays is actually a bug that we already have fix for, but our yum repo has been giving us trouble updating the past few days. Should hopefully have the repo fixed soon and we can push the fix so at the very least you will get a better message.

Thanks,

Andy

On May 1, 2017 at 4:33:22 PM, Casey Russell () wrote:

Group,

     I've recently upgraded two of my testing hosts to PS 4.0.  One of them participates in a number of remote meshes as well as my own mesh.  after the upgrade, I get the following error about once an hour in the /var/log/perfsonar/meshconfig-agent.log

2017/05/01 15:17:14 (23610) WARN> Agent.pm:363 perfSONAR_PS::MeshConfig::Agent::__configure_host - Multiple 'host' elements associated with the addresses on this machine: 164.113.32.49, ps-bryant-bw.perfsonar.kanren.net, ::1, 2001:49d0:23c0:1:0:0:0:10, 2001:49d0:23c0:6:0:0:0:49, 2001:49d0:23c0:6::49, 127.0.0.1, ps-bryant-lt.perfsonar.kanren.net, 164.113.32.141, 2001:49d0:23c0:1::10

2017/05/01 15:17:14 (23610) ERROR> Agent.pm:420 perfSONAR_PS::MeshConfig::Agent::__configure_host - Problem adding tasks: Problem adding test [MESHNAME] OWAMP: Can't call method "bind_maps" without a package or object reference at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/MeshConfig/Generators/perfSONARRegularTesting.pm line 405.

The first line there is largely cosmetic (or was in 3.5) it just deals with how the Mesh manager built the config file (using two host elements for my host instead of one).

The second line is the one that appears to be more problematic, and I can't pinpoint just what in the JSON file might be causing it to error out.  I've removed the Mesh name and inserted a variable to anonymize it a bit, since it's not my mesh (or mesh file) but if someone wants to see a link to the mesh .json file, hit me up and I'll send you a direct link.

Thoughts?

Sincerely,

Casey Russell

Network Engineer

785-856-9809

2029 Becker Drive, Suite 282
Lawrence, Kansas 66047