perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Bill,

Bruce and I exchanged some notes offline and found one place in the pscheduler code where IPv6 addresses weren't getting bracketed properly. That’s been fixed in our git repo and should at least solve part of the problem. RPM is on our testbed and hopefully should be in the main yum repo in the next day.

Could you provide some more details on what problems you are seeing with hosts that mix A and AAAA records?  Its quite possible there is something else happening as well.

Thanks,

Andy

On April 27, 2017 at 11:18:49 AM, Bill Owens () wrote:

Bruce,

Do the tests work if you put an IPv4 numeric address in the host box, instead of the name? I’ve run into what appears to be an issue with hosts that have both A and AAAA records, even if they’re only selected for IPv4.

Bill.

On 4/24/17, 11:44 AM, " on behalf of Curtis, Bruce" < on behalf of > wrote:

We have two perfsonar boxes and after the automatic upgrade to 4.0 some graphs stopped updating.

It looks like the common variable for the graphs that do not update is that perfsonar lists the IPv6 address under the host name.

I verified that I can run the throughput tests manually over IPv6 with the pscheduler command.

I do see lots of these error messages but haven’t verified that they are related to the problem.

Apr 23 04:12:41 perfsonar2 bwctld[28704]: FILE=sapi.c, LINE=391, BWLControlAccept(): Unable to read ClientGreeting message

These are our two hosts that exhibit the problem.

https://perfsonar2.ndsu.nodak.edu

https:perfsonar.ndsu.nodak.edu

Deleting the tests and adding them back with IPv4 set does not seem to result in working graphs either.


I also noticed the same problem on ps-border1-pt.lbl.gov to sites nersc-pt1-v6.es.net and bost-pt1-v6.es.net and sent email to the admin there and received a reply that they will add it to their list of issues to look into.
>

---
Bruce Curtis
Certified NetAnalyst II 701-231-8527
North Dakota State University