perfSONAR User Q&A and Other Discussion

[Joseph Bernard <>]

Just got a chance to clear out the java cache.  It works now!

Thanks,

Joseph B.

On Aug 21, 2013, at 4:53 PM, Aaron Brown <> wrote:

Hey Joseph,

Sometimes the web browser, or java installation likes to cache .jar files. I ran into that just now when verifying. Using the old -rc Applet, I got the negative numbers, but using the -rc4 Applet, I got correct values. Try clearing out the browser cache, or the java cache (though I dunno how to do the latter in a general manner…)

Cheers,

Aaron

On Aug 21, 2013, at 11:47 AM, Joseph Bernard <> wrote:

If I use web100clt, I get numbers that look correct with these new RPMs.  If I use the Java client, I still get crazy numbers.  What version of Java are you using?

Thanks,

Joseph B.

On Aug 19, 2013, at 3:15 PM, Aaron Brown <>

 wrote:

Hey Joseph,

Try these RPMs: http://ndb1.internet2.edu/~aaron/ndt-3.6.5.2-rc4.x86_64/

Cheers,

Aaron

On Aug 15, 2013, at 8:35 PM, Joseph Bernard <> wrote:

Will those RPMs work for el6.x86_64?

Thanks,
Joseph B.

On Aug 15, 2013, at 4:15 PM, Aaron Brown <>
wrote:

Would you folks be able to test out some newer NDT RPMs? They've been lightly tested by me (i.e. i got a couple successful tests out of them :))

You can grab the RPMs from http://ndb1.internet2.edu/~aaron/ndt-3.6.5.2-rc4.i386/

Download the ndt-server and ndt-client RPMs, and then do:

yum localinstall ndt-client-3.6.5.2-rc4.el5.centos.i386.rpm ndt-server-3.6.5.2-rc4.el5.centos.i386.rpm

You'll need to restart NDT after that by doing /etc/init.d/ndt restart

Cheers,
Aaron

On Aug 15, 2013, at 2:58 PM, Joseph Bernard <>
wrote:

That would explain my results when I tried it on a workstation with a 10G card.

client-to-server   5656.09Mb/s
server-to-client   -599769.5kb/s


Thanks,
Joseph B.


On Aug 15, 2013, at 2:31 PM, David Leibfritz <>
wrote:

I have been informed the NDT version 3.6.5.2 has a bug in the code recently
where the S2C byte counter was set to an 32 bit int value.  At 10 Gbps rates
this overflows with the obvious results.  When will perfSONAR get updated with
the NDT version that has this bug fix?