perfSONAR User Q&A and Other Discussion

["Andrew Lake" <>]

Hi,

The cause must be different than Carl’s looking at the generated URLs and commands. Do you get results when you run the following on your MaDDash host?

/opt/perfsonar_ps/nagios/bin/check_throughput.pl -u "http://bdw-clgr2pfs2.canarie.ca/esmond/perfsonar/archive"0 -w 0.9: -c 0.5: -r 86400 -s bdw-clgr2pfs2.canarie.ca -d bdw-hlfx1pfs2.canarie.ca -a bdw-clgr2pfs2.canarie.ca -p tcp --filter "bw-ignore-first-seconds:5”

I get results when run that from my laptop, so maddash should too since that’s exactly what it runs. You may want to verify that the system time on your MaDDash host isn’t way off (like days off) as this could affect the calulcated time range when it runs the command above. Also verify that you have the 3.5 version of the perl-perfSONAR_PS-Nagios package. 

Hope that helps,

Andy

On Wed, Oct 21, 2015 at 4:30 PM, Amit Khare <> wrote:

Hi Andy,

I am having the same issue as Carl, our throughput tests are showing
Œunable to retrieve data¹ however when I click on the boxes, graphs appear
to have test results
(http://otwa3pfs1.canarie.ca/maddash-webui/index.cgi?dashboard=Mesh%20Sites
). I tried setting Œfilter tool name¹ to 0 but it didn¹t resolve the
issue. Are there any further troubleshooting steps that I can try. Thanks,

Amit


Amit Khare
Network Engineer | CANARIE <http://canarie.ca/> |
<mailto:> | office: 613.943.5377 | mobile:
613.404.8696 | NOC: 613.944.5612 | @canarie_inc
<http://twitter.com/canarie_inc>






On 2015-10-08, 09:51, "Carl Hayter" <> wrote:

>Setting 'filter_tool_name' to 0 did the trick, I have many colors now.
>
>Thanks,
>Carl
>
>On Thu, Oct 08, 2015 at 05:59:50AM -0700, Andrew Lake wrote:
>> Hi Carl,
>>
>> Assuming it doesn¹t go green, what happens if you set
>>³filter_tool_name² to 0
>> in /opt/perfsonar_ps/mesh_config/etc/gui_agent_configuration.conf and
>>then
>> re-run /opt/perfsonar_ps/mesh_config/bin/generate_gui_configuration?
>>It¹s
>> trying to only grab iperf3 tests (which is good) but I can¹t tell if
>>the tool
>> name generated matchs what¹s in your MA.
>>
>> Thanks,
>> Andy
>>
>>
>>
>>
>>
>> On Thu, Oct 8, 2015 at 8:23 AM, Garnizov, Ivan (RRZE)
>><>
>> wrote:
>>
>> Hi Carl,
>>
>> Have no worries. It will go green soon, unless sudden failures
>>appear. You
>> have almost, but not quite, a full week of successful measurements.
>>On the
>> charts I looked.
>>
>> Best regards,
>> Ivan
>>
>> -----Original Message-----
>> From:
>> [mailto:] On Behalf Of Carl
>>Hayter
>> Sent: Mittwoch, 7. Oktober 2015 21:08
>> To:
>> Subject: [perfsonar-user] Maddash only working halfway
>>
>> I'm having a bit of a weird issue with maddash. We have 8 perfsonar
>>boxes
>> (updated to 3.5) and I installed maddash one one of them, created a
>>mesh
>> configuration and configured all the machines to pull it down,
>>created the
>> maddash config, and crossed my fingers...
>>
>> Funny thing is, on the dashboard, the OWAMP tests show up fine. The
>> throughput tests all stay orange and say 'Unable to find any tests
>>with
>> data in the given time range ...'.
>>
>> Looking at individual boxes, the tests in the mesh config are
>>running and
>> collecting data. If I go to hpc-perfsonar.usc.edu I can view the
>>graph for
>> the test against phe-perfsonar.usc.edu, and if I go to
>> phe-perfsonar.usc.edu I can view the graph for the test against
>> hpc-perfsonar.usc.edu.
>>
>> On the maddash page, the HPC - PHE cells are orange and have the
>>error
>> message, if I click on the cells I do see a graph with the correct
>>test
>> data.
>>
>>
>>http://hpc-perfsonar.usc.edu/maddash-webui/index.cgi?dashboard=USC%20TEN-
>>II
>>
>>
>>http://hpc-perfsonar.usc.edu/maddash-webui/details.cgi?uri=/maddash/grids
>>/
>> USC+TEN-II+-+USC+TEN-II+Throughput+Testing/phe-perfsonar.usc.edu/
>> hpc-perfsonar.usc.edu/Throughput
>>
>>
>>http://hpc-perfsonar.usc.edu/maddash-webui/details.cgi?uri=/maddash/grids
>>/
>> USC+TEN-II+-+USC+TEN-II+Throughput+Testing/hpc-perfsonar.usc.edu/
>> phe-perfsonar.usc.edu/Throughput+Alternate+MA
>>
>> If I do a `curl
>>http://phe-perfsonar.usc.edu/esmond/perfsonar/archive/`
>> I get a bunch of JSON data, same for hpc-perfsonar.usc.edu.
>>
>> If I run the `check_throughput.pl` nagios script (I think this is
>>how the
>> maddash data is acquired...), I get seemingly normal data.
>>
>> ~~~ on hpc-perfsonar.usc.edu ~~~
>>
>> H=hpc-perfsonar.usc.edu
>> P=phe-perfsonar.usc.edu
>> C='/opt/perfsonar_ps/nagios/bin/check_throughput.pl -p tcp --tool
>>bwctl/
>> iperf3 -w 7: -c 20: -r 86400'
>>
>> # PHE->HPC from PHE ma
>> $C -s $P -d $H -a $P -u http://$P/esmond/perfsonar/archive
>> PS_CHECK_THROUGHPUT CRITICAL - Average throughput is 9.840Gbps |
>>Count=9;;
>> Min=9.60168;; Max=9.90942;; Average=9.84042555555556;;
>>Standard_Deviation=
>> 0.121737880414458;;
>>
>> # HPC->PHE from PHE ma
>> $C -s $H -d $P -a $P -u http://$P/esmond/perfsonar/archive
>> PS_CHECK_THROUGHPUT CRITICAL - Average throughput is 9.273Gbps |
>>Count=7;;
>> Min=5.64209;; Max=9.9051;; Average=9.27343285714286;;
>>Standard_Deviation=
>> 1.60169745801878;;
>>
>> # HPC->PHE from HPC ma
>> $C -s $H -d $P -a $H -u http://$H/esmond/perfsonar/archive
>> PS_CHECK_THROUGHPUT CRITICAL - Average throughput is 9.816Gbps |
>>Count=4;;
>> Min=9.76832;; Max=9.83687;; Average=9.8162625;; Standard_Deviation=
>> 0.0322087476473979;;
>>
>> # PHE->HPC from HPC ma
>> $C -s $P -d $H -a $H -u http://$H/esmond/perfsonar/archive
>> PS_CHECK_THROUGHPUT CRITICAL - Average throughput is 9.542Gbps |
>>Count=4;;
>> Min=8.44071;; Max=9.9097;; Average=9.54223;; Standard_Deviation=
>> 0.734346699182354;;
>>
>> ~~~
>>
>> So, how/why does my dashboard show the OWAMP results correctly but
>>not the
>> Throughput results?
>>
>> I've attached the 'usc-tenii.conf' (mesh config file),
>>'usc-tenii.json'
>> (via /opt/perfsonar_ps/mesh_config/bin/generate_configuration), and
>> 'maddash.yaml' (via /opt/perfsonar_ps_mesh_config/bin/
>> generate_gui_configuration).
>>
>> Any ideas?
>>
>> ----
>> Carl Hayter
>> ITS - Data Network Operations
>> University of Southern California
>>
>>