perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi George,

This related to the BWCTL update I sent a note about this morning. Your test is not detecting pScheduler on both ends and falling back to bwctl+iperf3. Since bwctl does not think it can use iperf3, bad stuff happens and you get the weird result you see below. Saw the exact same error multiple times while debugging the BWCTL issues. The new BWCTL packages should be in the main I2 mirror right now, so if you do a yum update you should get the new packages. You need the update on both ends for it to work.

Thanks,

Andy

On March 16, 2018 at 11:35:10 AM, Uhl, George D. (GSFC-423.0)[SGT INC] () wrote:

I did a yum update on three of my pS testpoints that are currently still running  Centos 6.9.   I’m seeing the following errors on some of my tests:

==========

# pscheduler result https://enpl-pt2-10g.eos.nasa.gov/pscheduler/tasks/84b5408c-93c9-4656-b790-ad0771d73f06/runs/18a23044-8273-4b36-9779-9d42d988ef11

2018-03-16T11:06:57-04:00 on enpl-pt2-10g.eos.nasa.gov with bwctliperf3:

throughput --source enpl-pt2-10g.eos.nasa.gov --dest perfnsidc.colorado.edu

Run failed.

Diagnostics from enpl-pt2-10g.eos.nasa.gov:

    

Error from enpl-pt2-10g.eos.nasa.gov:

    Unable to parse iperf3 output as JSON: No JSON object could be decoded

==========

I’ve attached  a text file  that contains the files that were updated during the yum update and the perfsonar log file (with debug turned on)

Thanks,

George