perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

Actually, I take back needing maddash.out. I was following a link you providedin your original email and NONE of the details were loading, but looks like you changed some names since then. Clicking through directly I see the issue you reference where everything but the graphs look fine. What version of the "perfsonar-graphs" package are you using? The following URLs should look exactly the same, but they don't. I am wondering if maybe you have an old perfsonar-graphs (3.5.1.3 is the latest):

Doesn't Work:

http://ps-dashboard.npidev.psu.edu/perfsonar-graphs/graphWidget.cgi?url="http://128.118.46.225/esmond/perfsonar/archive&source=172.31.0.218&dest=172.31.0.50&ipversion=4&protocol=tcp

Works:

http://ps-dashboard.es.net/perfsonar-graphs/graphWidget.cgi?url="http://128.118.46.225/esmond/perfsonar/archive&source=172.31.0.218&dest=172.31.0.50&ipversion=4&protocol=tcp

Hope that helps,

Andy

On Thu, Jul 28, 2016 at 11:47 AM, Andrew Lake <> wrote:

Hi Ken,

Sorry for the delay, looks like data is getting written fine (since you have non-orange boxes) so that’s good, looks like maybe just a display issue (possibly even a bug with the MaDDash version you are beta testing). Could you send me /var/log/maddash/maddash-server.out?

Thanks,

Andy

On July 27, 2016 at 4:40:34 PM, Kenneth D Miller II () wrote:

Hi,

There has not been any updates to this regular_testing.log since the 3.5 auto update from March. I believe the new file name is /var/log/perfsonar/regulartesting.log. Its on error only by default, but when I change /etc/perfsonar/regulartesting.conf from INFO to DEBUG, I can see tests coming through on blue1 and white1 nodes. Below is an test entry.

I have the central MA running now, but the graph history is still not working. It's still producing the same webservice error.

/etc/init.d/perfsonar-regulartesting start: perfSONAR Regular Testing started
[root@blue-rtm perfsonar]# tail -n100 -f /var/log/perfsonar/regulartesting.log
'duplicate_packets' => '0',
'packet_count' => '600'
}, 'perfSONAR_PS::RegularTesting::Results::LatencyTest' );
2016/07/27 16:29:49 (13208) DEBUG> EsmondBase.pm:202 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::add_data - esmond data: $VAR1 = [
{
'ts' => 1469624230,
'val' => [
{
'event-type' => 'packet-count-sent',
'val' => '600'
},
{
'event-type' => 'histogram-owdelay',
'val' => {
'0.6' => '1',
'0.4' => '226',
'0.5' => '373'
}
},
{
'event-type' => 'histogram-ttl',
'val' => {
'253' => '88'
}
},
{
'event-type' => 'packet-duplicates',
'val' => '0'
},
{
'event-type' => 'packet-loss-rate',
'val' => {
'denominator' => '600',
'numerator' => '0'
}
},
{
'event-type' => 'packet-count-lost',
'val' => '0'
},
{
'event-type' => 'time-error-estimates',
'val' => '0.003349'
}
]
}
];
2016/07/27 16:29:49 (13208) DEBUG> EsmondBase.pm:250 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::send_http_request - Writing to esmond at http://128.118.46.225/esmond/perfsonar/archive/
2016/07/27 16:29:49 (13208) DEBUG> EsmondBase.pm:251 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::send_http_request - Esmond request: {"data":[{"ts":1469624230,"val":[{"event-type":"packet-count-sent","val":"600"},{"event-type":"histogram-owdelay","val":{"0.6":"1","0.4":"226","0.5":"373"}},{"event-type":"histogram-ttl","val":{"253":"88"}},{"event-type":"packet-duplicates","val":"0"},{"event-type":"packet-loss-rate","val":{"denominator":"600","numerator":"0"}},{"event-type":"packet-count-lost","val":"0"},{"event-type":"time-error-estimates","val":"0.003349"}]}]}
2016/07/27 16:29:49 (13208) DEBUG> EsmondBase.pm:280 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::send_http_request - Esmond response: ""

Thanks,
Ken

----- Original Message -----
> From: "Szymon Trocha" <>
> To: "Kenneth D Miller II" <>,
> Sent: Wednesday, July 27, 2016 5:02:00 AM
> Subject: Re: [perfsonar-user] Error retrieving data from the webservice

> W dniu 26.07.2016 o 22:57, Kenneth D Miller II pisze:
>> Hi,
>>
>> In moving our state wide perfsonar deployment to a central MA and Maddash, I'm
>> getting an error when I click into a graph history detail from Maddash.
>> Error retrieving data from the webservice.
>>
>> The initial maddash is here:
>> http://ps-dashboard.npidev.psu.edu/maddash-webui/index.cgi?dashboard=Penn%20State%20RTM%20Mesh%20Config
>>
>> Detail page with error:
>> http://ps-dashboard.npidev.psu.edu/maddash-webui/details.cgi?uri=/maddash/grids/Penn+State+RTM+Mesh+Config+-+Penn+State+IPv4+Throughput+Testing/blue1.rtm.tns.its.psu.edu/tb7.rtm.tns.its.psu.edu/Throughput+Reverse
>>
>>
>
> Hi Kenneth,
>
> Can you verify if the hosts properly downloaded the mesh config file and
> are actually storing data into central MA? For instance looking at the
> Blue1 or White1 node's /var/log/perfsonar/regular_testing.log ?
>
> Regards,
>
> --
> Szymon Trocha
>
> Poznań Supercomputing & Netw. Center ::: NETWORK OPERATION CENTER
> Tel. +48 618582022 ::: http://noc.man.poznan.pl