perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

Would it be possible to add a few of the IPv6 tests back? It looks like some type of archiving issue. My guess is that its is filling the IPv6 address in the archive URL and either the archive is not listening on IPV6, the v6 filters are blocking 443 or its not formatting the URL properly. If you add the task back I can take a look and see what it does.

Thanks,
Andy

On Fri, Sep 21, 2018 at 2:58 PM Curtis, Bruce <> wrote:

  We had some problems with IPv6 on our perfsonar nodes so we changed our tests to only use IPv4.

  I thought the problems had been fixed on newer versions but we couldn’t upgrade until we upgraded to Centos 7.

  We have not upgraded to Centos 7 and Perfsonar 4.1 but are still seeing issues with IPv6 tests.


Here is an example from /var/log/messages. It looks like the test succeeds but is not archived.

Sep 20 20:36:49 perfsonar2 journal: runner INFO     2547: With iperf3: throughput --source 2001:4930:91::125 --ip-version 6 --dest perfsonar1.ccast.ndsu.edu --source-node [2001:4930:91::125] --dest-node perfsonar1.ccast.ndsu.edu
Sep 20 20:37:06 perfsonar2 journal: runner INFO     2547: Run succeeded.
Sep 20 20:37:23 perfsonar2 journal: archiver WARNING  207: Failed to archive https://localhost/pscheduler/tasks/4d2fdd27-3278-450b-90da-e212c8fbe525/runs/64524ab9-7d46-40fe-ae5e-d333ebd9a932 to esmond: Archiver permanently abandoned registering test after 1 attempt(s): 500: Invalid JSON returned
Sep 20 20:37:23 perfsonar2 journal: archiver WARNING  207: Gave up archiving https://localhost/pscheduler/tasks/4d2fdd27-3278-450b-90da-e212c8fbe525/runs/64524ab9-7d46-40fe-ae5e-d333ebd9a932 to esmond


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