perfSONAR User Q&A and Other Discussion

[Lixin Liu <>]

Hi Andy,

Actually the bandwidth results show up too, but my test server was having
trouble running tests during the last few days. So I had to change length
to a larger value to display the past results.

So this is what I use:

OW Latency:

maUrl:
   default: "http://%row/esmond/perfsonar/archive";
            graphUrl:
"http://maddash-server-name/serviceTest/graphWidget.cgi?url=%maUrl&dest=%co
l&source=%row&length=14400"
            command: "/opt/perfsonar_ps/nagios/bin/check_owdelay.pl -u
%maUrl -w 0 -c 0 -r 1800 -l -p -s %row -d %col²

Throughput:

maUrl:
   default: "http://%row/esmond/perfsonar/archive";
            graphUrl:
"http://maddash-server-name/serviceTest/graphWidget.cgi?url=%maUrl&dest=%co
l&source=%row&length=2592000"
            command:  "/opt/perfsonar_ps/nagios/bin/check_throughput.pl -u
%maUrl -w .1: -c .01: -r 86400 -s %row -d %col²

It would be nice if Maddash document is updated to display 3.4 test
results.


Cheers,


Lixin.

On 2014-10-14, 2:45 PM, "Lixin Liu" 
<>
 wrote:

>Hi Andy,
>
>I asked the same question a few days ago and did not get an answer.
>I now figured out how to show the graph. The graphUrl should be
>changed to
>
>graphUrl: "<server
>name>/serviceTest/graphWidget.cgi?url=%maUrl&dest=%col&source=%row"
>
>and of course reverse row/col for reverse delay.
>
>This works for latency graph, but I am still unable to get bandwidth
>graph.
>
>Thanks,
>
>Lixin.
>
>> -----Original Message-----
>> From: 
>> 
>>  [
>> ]
>>  On Behalf Of Andrew Lake
>> Sent: October-14-14 1:53 PM
>> To: Jeremy Palmer
>> Cc: 
>> 
>> Subject: Re: [perfsonar-user] PerfSONAR Dashboard broken after upgrade
>>to
>> 3.4
>>
>> Hi Jeremy,
>>
>> You need to change the url to http://%row/esmond/perfsonar/archive/
>>
>> That should bring everything back, sorry for the inconvenience.
>>
>> Thanks,
>> Andy
>>
>>
>> On Oct 14, 2014, at 4:27 PM, Jeremy Palmer 
>> <>
>> wrote:
>>
>> > Our dashboard completely stopped working after upgrading to 3.4. All
>> > boxes
>> in the grid are now showing the orange "Unable to retrieve data" color.
>> I'm
>> getting a ton of errors like the following in the maddash-
>> server.netlogger.log file:
>> > level=INFO ts=2014-10-14T08:20:06.313974Z
>> event=maddash.RunCheckJob.execute.runCheck.end
>> guid=0e7c7ee5-840b-487f-8e26-
>> c662648f45ad resultMsg=" Unable to contact MA. Please check that the MA
>>is
>> running and the URL is correct."
>> >
>> > The maURL in my maddash.yaml file is:
>> > maUrl: default: "http://%row:8085/perfSONAR_PS/services/pSB";
>> >
>> > However, none of my hosts seem to be listening on tcp/8085 anymore
>>since
>> the upgrade.
>> >
>> > Was working fine before the upgrade. Is there something that needs to
>>be
>> done to convert the dashboard config to work with the new version?
>> >
>> > --
>> > Jeremy Palmer
>> > Senior Network Engineer
>> > ViaWest, Inc.
>> > Office: 720.891.1045
>> > Fax: 303-874-5236
>> > http://www.viawest.com
>> >
>