Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade


Chronological Thread 
  • From: Andrew Lake <>
  • To: Bill Owens <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade
  • Date: Fri, 28 Apr 2017 06:52:42 -0700
  • Ironport-phdr: 9a23:S6pW4BNgeEZeKBAkRqcl6mtUPXoX/o7sNwtQ0KIMzox0Ivj+rarrMEGX3/hxlliBBdydsKMazbaG+P6/EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT68bL9oIxi7rgrdu8gUjIB/Nqs/1xzFr2dSde9L321oP1WTnxj95se04pFu9jlbtuwi+cBdT6j0Zrw0QrNEAjsoNWA1/9DrugLYTQST/HscU34ZnQRODgPY8Rz1RJbxsi/9tupgxCmXOND9QL4oVTi+6apgVQTlgzkbOTEn7G7Xi9RwjKNFrxKnuxx/2JPfbIWMOPZjYq/RYdYWSGxPUcZLUyxKH52yYY0BAeEcOepUtofwq14IoBCjBwejGfnvxydIiHD006001OsuHw/F0gI9AdwBrG/Zo8/pOKoIS+241rXEwDfFYvhL2Tn98o/IchU5rPyQW7J/bNDRxlchFgjYiFufs4/lMC2I3ekKqWeb6fdvVOK0hmE5sAF9uD6vydkwioTQgI8e117K9SJ8wIkvJN24TlZ2bsC/EJdKsSGVKZd2TtsmQ25zvCY20LIGuZmlfCQSzpQnwAPQZOaEc4SS/B3sSfuRLS99hHJ/frKwmQqy/VKlyuLnTMW7zExFoyxYmdfPrnAAzwHf5taER/dn8EqtwzmC2x3J5uxFIk04jajWJpE7zrItiJYesV7PEyz4lUnsjqKaa0Mp8fWy5ev9eLXpvJqcOpd0ig7gNqQundSyAeomPQUARWSb/f+z1Ln58U32R7VKkOU6kqjfsJ/EOcQWvrO1DxFW34o55RuzFTir3MkCkXQGL19JYBeHgJLoO1HKLvD4F/C/g1G0nThxwfDJI73gD47TIXjYirvhe6hy61JExAop0d9f/45UCq0GIP/rQk/+qsbYDhEiMwyzxeboEs992poDWWKUHKCZKrjfsVuJ5uI0P+mMf5EZtCz8K/gj+/7hk2U5mVkDcqm1w5cbcm63Eel7IxbRXX25qNYFFS8toQc4V6S+j0KPVyV7YWepUrg66y19D5ipW9TtXIeo1ZWH0D22AdVyb2NLQgSFF3v5X4ifHfEBdHTBcYdajjUYWO35GMca3ha0uVq/kuI8Iw==

Hi Bill,

That issue looks different from the one one you reported back during the RC. The one from the RC was a validation error of the test parameters, the new one looks to be some type of connection error or possibly the URL formatting error that got fixed (though that usually resulted in a different error). While debugging some of this I did find a place in the meshconfig-agent where force_ipv4 was getting ignored for some tests so that might be part of it as well. I have RPMs with all these fixes but the infrastructure that builds and updates our yum repo is giving us fits. Once we get that corrected I should be able to get the new RPMs out and we can see what that fixes and if anything is leftover. 

Thanks,
Andy



On April 27, 2017 at 12:58:31 PM, Curtis, Bruce () wrote:


> On Apr 27, 2017, at 10:17 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.


I do have a test I set up a long time ago to bdw-uofm-fg.mrnet.mb.ca at 192.139.69.54, 2001:410:2000::4 that is defined with just the IPv4 number and that continues to work. However I’m not sure that bdw-uofm-fg.mrnet.mb.ca had an IPv6 address when I set up the test.

I see that 192.139.69.54 does not have a reverse DNS entry.

<target>
address 192.139.69.54
<override_parameters>
type bwctl
force_ipv4 1
</override_parameters>
description MRnet, Winnipeg, MB, CA
</target>

$ host 192.139.69.54
Host 54.69.139.192.in-addr.arpa. not found: 3(NXDOMAIN)


I added a new test for 131.243.246.66 ps-border1-pt.lbl.gov and that test has been added to /etc/perfsonar/meshconfig-agent-tasks.conf

<target>
address 131.243.246.66
<override_parameters>
type bwctl
force_ipv4 1
</override_parameters>
description test LBL
</target>

But the test results do not appear on the public dashboard.

131.243.246.66 does have a reverse DNS entry

host 131.243.246.66
66.246.243.131.in-addr.arpa domain name pointer ps-border1-pt.lbl.gov.


>
> 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
>
>
>

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




Archive powered by MHonArc 2.6.19.

Top of Page