Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Andrew Lake <>
- To: "" <>, Paul Murray <>
- Subject: Re: [perfsonar-user] Problem participating in 2nd dashboard.
- Date: Mon, 9 May 2016 09:15:47 -0400
Hi Paul,
First off, thanks for digging down and providing all the debugging output. Looks like the issue is that in the Ivy+ JSON file that the field “no_agent”is set to 1 for ps-40g-hpr01.stanford.edu. That field indicates that this host does not initiate any tests and is generally intended for hosts included in a test mesh that don’t actually read the JSON file. Look like someone just needs to set “no_agent”to 0 (or just remove the definition) for the stanford host in the central Ivy+ mesh config file and regenerate the JSON. Your host should then update regulartesting.conf accordingly. Hope that helps.
Thanks, Andy
On May 6, 2016 at 4:34:20 PM, Paul Murray () wrote:
Hello,
When I comment in or out
the CENIC json from the meshconfig-agent file it is automatically
removed from or added to regulartesting.conf correctly. So the
update looks to work correctly but it is only working correctly for
CENIC’s json file.
It
just doesn’t seem to be working with the Ivy+ one. Whenever it
reads in this json file it states that the regulartesting.conf is
unchanged in the debug despite reading in the json:
Removing both at same
time (no mesh configuration):
2016/04/27 16:07:09
(132241) DEBUG> ConfigFile.pm:109
perfSONAR_PS::RegularTesting::Utils::ConfigFile::parse_file -
Setting variable: type
2016/04/27 16:07:09
(132241) DEBUG> ConfigFile.pm:109
perfSONAR_PS::RegularTesting::Utils::ConfigFile::parse_file -
Setting variable: username
2016/04/27 16:07:09
(132241) DEBUG> ConfigFile.pm:92
perfSONAR_PS::RegularTesting::Utils::ConfigFile::parse_file -
Ending block: measurement_archive
2016/04/27 16:07:09
(132241) DEBUG> ConfigFile.pm:109
perfSONAR_PS::RegularTesting::Utils::ConfigFile::parse_file -
Setting variable: measurement_archive
2016/04/27 16:07:09
(132241) DEBUG> Agent.pm:523
perfSONAR_PS::MeshConfig::Agent::__compare_file - Checking for
changes in /etc/perfsonar/regulartesting.conf
2016/04/27 16:07:09
(132241) DEBUG> Agent.pm:528
perfSONAR_PS::MeshConfig::Agent::__compare_file - Reading
/etc/perfsonar/regulartesting.conf
2016/04/27 16:07:09
(132241) INFO> Agent.pm:484
perfSONAR_PS::MeshConfig::Agent::__write_file -
/etc/perfsonar/regulartesting.conf is unchanged.
2016/04/27 16:07:09
(132241) DEBUG> Agent.pm:169
perfSONAR_PS::MeshConfig::Agent::__send_error_messages - Sending
error messages is disabled
Adding in only Ivy+
(note it says on write_file that regulartesting.conf is unchanged
when doing the compare_file):
2016/04/27 16:10:18
(132473) DEBUG> HTTPS.pm:65
perfSONAR_PS::Utils::HTTPS::https_get - Connecting
to: perfsonar-ma.princeton.edu: 443
2016/04/27 16:10:19
(132473) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Bandwidth
2016/04/27 16:10:19
(132473) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Ping
2016/04/27 16:10:19
(132473) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Delay
2016/04/27 16:10:19
(132473) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Traceroute
2016/04/27 16:10:19
(132473) DEBUG> Agent.pm:523
perfSONAR_PS::MeshConfig::Agent::__compare_file - Checking for
changes in /etc/perfsonar/regulartesting.conf
2016/04/27 16:10:19
(132473) DEBUG> Agent.pm:528
perfSONAR_PS::MeshConfig::Agent::__compare_file - Reading
/etc/perfsonar/regulartesting.conf
2016/04/27 16:10:19
(132473) INFO> Agent.pm:484
perfSONAR_PS::MeshConfig::Agent::__write_file -
/etc/perfsonar/regulartesting.conf is unchanged.
2016/04/27 16:10:19
(132473) DEBUG> Agent.pm:169
perfSONAR_PS::MeshConfig::Agent::__send_error_messages - Sending
error messages is disabled
Adding back in CENIC
(sees that regulartesting.conf has indeed changed and it does add
in the CENIC mesh hosts but not the Ivy+):
2016/04/27 16:11:39
(132552) DEBUG> HTTPS.pm:65
perfSONAR_PS::Utils::HTTPS::https_get - Connecting
to: ps-dashboard.cenic.net: 443
2016/04/27 16:11:40
(132552) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: Throughput 40G-connected
2016/04/27 16:11:40
(132552) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: Traceroute 40G-connected
2016/04/27 16:11:40
(132552) DEBUG> HTTPS.pm:65
perfSONAR_PS::Utils::HTTPS::https_get - Connecting
to: perfsonar-ma.princeton.edu: 443
2016/04/27 16:11:40
(132552) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Bandwidth
2016/04/27 16:11:40
(132552) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Ping
2016/04/27 16:11:40
(132552) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Delay
2016/04/27 16:11:40
(132552) DEBUG> perfSONARRegularTesting.pm:167
perfSONAR_PS::MeshConfig::Generators::perfSONARRegularTesting::add_mesh_tests
- Adding: IvyPlus Traceroute
2016/04/27 16:11:40
(132552) DEBUG> Agent.pm:523
perfSONAR_PS::MeshConfig::Agent::__compare_file - Checking for
changes in /etc/perfsonar/regulartesting.conf
2016/04/27 16:11:40
(132552) DEBUG> Agent.pm:528
perfSONAR_PS::MeshConfig::Agent::__compare_file - Reading
/etc/perfsonar/regulartesting.conf
2016/04/27 16:11:40
(132552) DEBUG> Agent.pm:531
perfSONAR_PS::MeshConfig::Agent::__compare_file -
/etc/perfsonar/regulartesting.conf changed
2016/04/27 16:11:40
(132552) DEBUG> Agent.pm:488
perfSONAR_PS::MeshConfig::Agent::__write_file - Writing
/etc/perfsonar/regulartesting.conf
2016/04/27 16:11:51
(132552) DEBUG> Agent.pm:169
perfSONAR_PS::MeshConfig::Agent::__send_error_messages - Sending
error messages is disabled
I
can’t figure out where to turn on debug to see if the json read for
Ivy+ is failing at a certain point. It definitely only updates for
the CENIC json.
As other hosts are
participating in the Ivy+ dashboard I believe the json file is
correct.
Any
suggestions?
Thanks,
Paul
* * * * *
Paul Murray
Networking Systems
|
Archive powered by MHonArc 2.6.16.