Skip to Content.
Sympa Menu

perfsonar-user - Re: Fwd: [perfsonar-user] IPV6 tests doesn't run/show

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: Fwd: [perfsonar-user] IPV6 tests doesn't run/show


Chronological Thread 
  • From: Andrew Lake <>
  • To: , Eraldo Jr <>
  • Subject: Re: Fwd: [perfsonar-user] IPV6 tests doesn't run/show
  • Date: Tue, 23 Jan 2018 13:21:34 -0500
  • Ironport-phdr: 9a23:CDmyfRPMXEsArUjKR0cl6mtUPXoX/o7sNwtQ0KIMzox0Iv/6rarrMEGX3/hxlliBBdydt6odzbKO+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1Ov71GonPhMiryuy+4ZLebxlViDanfb9+MAi9oBnMuMURnYZsMLs6xAHTontPdeRWxGdoKkyWkh3h+Mq+/4Nt/jpJtf45+MFOTav1f6IjTbxFFzsmKHw65NfqtRbYUwSC4GYXX3gMnRpJBwjF6wz6Xov0vyDnuOdxxDWWMMvrRr0yRD+s7bpkSAXwhSkHNTE5/mbZhcN+gqxYvRyvuQBwzpXOb42JLvdzZLnQcc8YSGdHQ81fVzZBAoS5b4YXE+cBO/tXr5PjqFoAsBCwAxOjBODxxTRVgXL5x6s63PkhEAzdwgMgBMgCsHLKo9XpLaofV/2+wqfPzTXGdfxW2DH95ZDWfRA6u/2MW6x/cdbJxUksFgPKlEufpZb/PzOIzugNsm6b7+RmVe61im4ntxl9ojmpxssykonEiJgZyl7e9Slh24Y1OMe4SEBgYdG+CptfrTuWN41yQs86X25noz46yrMctZGgZigHzoksyR3Ha/GfboSE/BHuWPyfLDtii39pZaizihSv/US41OHwSs253ExJoydFiNXAqG0B2hPJ5sWFVPdw+Fqq1yyV2ADJ8O5EJFg5larFJJ4lxb49jpQTvlrMEyPsnEX5l6uWel8r+uiv9eTrerTmppmCOI9okgzyL7oil8+lDek2KAQDUHWX9f6+2bH+5UH5Ra9FjvwykqnXqpDaIsEbq7ajDA9Tz4ki6w2yACm90NgCm3kIMk5FdAqdj4f1I1HOPOz4DfCnjlS0jjhr3f7GPqbmApXLNHfDiq7tfatm60FC0go+1tRf55NPCrEdO/L/RFX9tN3eDh8lLQO02eDnB8th1o8AQ26AHLKWML6B+WOPs/oiOeeXY4kconPgMPU/z//okXIjn1IBJ++k0YZTIF2iF/BqJA27ezK4i9wMCnwNswgWTefuj0COFzVUYiDhcbg742QSDo68AJiLYomujfTV1SG3D7VbfSZAB0zaQiSgTJmNR/pZMHHaGcRmiDFRDbU=

Hi Eraldo,

A couple observations:

- From the error message I assume your host is ps02.cat.cbpf.br (152.84.101.142, 2804:1f10:8000:801::142). It looks like at least some of the error messages are because the ipv6 address is trying to test to a hostname without a AAAA record, so it can't do IPv6, but don't think that’s the only issue.

- If I look at https://ps02.cat.cbpf.br/pscheduler/tasks?pretty&expanded I don’t see any tests with ip-version set to 6 or using your ipv6 address

- I was able to schedule a test from the command-line using ipv6: pscheduler task throughput --source lbl-pt1-v6.es.net --dest 2804:1f10:8000:801::142

- I see from http://ps02.cat.cbpf.br/toolkit/services/host.cgi?method=get_summary you have some remote meshes defined, but they don’t explicitly setup any IPv6 addresses as fas as I can tell. How are the IPv6 tests that are missing configured? are they additional tests you configured through the GUI? If no maybe send me /etc/perfsonar/meshconfig-agent-tasks.conf and I can see what you have configured.

Thanks,
Andy


On January 16, 2018 at 7:25:38 PM, Eraldo Jr () wrote:



Begin forwarded message:

From: Eraldo Jr 
Subject: Re: [perfsonar-user] IPV6 tests doesn't run/show
Date: 15 January 2018 14:06:27 GMT-2
To: Szymon Trocha 

Are you seeing any powstream or iperf processes running in the system related to these IPv6 addresses (via ps -ef)?

No.

Let's check if data is written to the database. Are you able to locate any of the IPv6 addresses when you put http://your_hostpl/esmond/perfsonar/archive/?format=json into web browser?

No

Any errors in logs?



pscheduler.log 
Jan 15 13:52:16 ps02 archiver WARNING  892774: Failed to archive https://localhost/pscheduler/tasks/bdd0dfda-76e7-4a91-ae54-7e0921e78e99/runs/cfb0fa48-5f5d-46df-8a26-d28c493a0c65 to esmond: 400: Invalid JSON returned
Jan 15 13:52:17 ps02 archiver WARNING  892777: Failed to archive https://localhost/pscheduler/tasks/bdd0dfda-76e7-4a91-ae54-7e0921e78e99/runs/cfb0fa48-5f5d-46df-8a26-d28c493a0c65 to esmond: 400: Invalid JSON returned
Jan 15 13:52:37 ps02 archiver WARNING  892776: Failed to archive https://localhost/pscheduler/tasks/bdd0dfda-76e7-4a91-ae54-7e0921e78e99/runs/cfb0fa48-5f5d-46df-8a26-d28c493a0c65 to esmond: 400: Invalid JSON returned
Jan 15 13:52:38 ps02 archiver WARNING  892775: Failed to archive https://localhost/pscheduler/tasks/bdd0dfda-76e7-4a91-ae54-7e0921e78e99/runs/cfb0fa48-5f5d-46df-8a26-d28c493a0c65 to esmond: 400: Invalid JSON returned
Jan 15 13:59:09 ps02 archiver WARNING  893049: Failed to archive https://localhost/pscheduler/tasks/28cc8be6-1c21-40b0-896d-4ccaea47d9c2/runs/e9b95e81-4a29-4f06-8478-3cac02dd8dbc to esmond: 400: Invalid JSON returned

owamp_bwctl.log
Jan 15 14:02:57 ps02 bwctld[8533]: FILE=sapi.c, LINE=391, BWLControlAccept(): Unable to read ClientGreeting message
Jan 15 14:02:59 ps02 bwctld[8537]: FILE=sapi.c, LINE=391, BWLControlAccept(): Unable to read ClientGreeting message
Jan 15 14:03:01 ps02 bwctld[8552]: FILE=sapi.c, LINE=391, BWLControlAccept(): Unable to read ClientGreeting message
Jan 15 14:03:08 ps02 bwctld[8664]: FILE=sapi.c, LINE=391, BWLControlAccept(): Unable to read ClientGreeting message


meshconfig-agent.log

2018/01/15 12:30:39 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test throughput(2804:1f10:8000:801::142->btw-bw.grid.kiae.ru), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Can't find pScheduler or BWCTL on 2804:1f10:8000:801::142

2018/01/15 12:30:39 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test throughput(btw-bw.grid.kiae.ru->2804:1f10:8000:801::142), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Can't find pScheduler or BWCTL on 2804:1f10:8000:801::142

2018/01/15 12:30:39 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test throughput(152.84.101.142->ps.lhcopn-ps.surfsara.nl), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/01/15 12:30:39 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test throughput(2804:1f10:8000:801::142->ps.lhcopn-ps.surfsara.nl): 400 BAD REQUEST: Neither the source nor destination is running pScheduler.
2018/01/15 12:30:39 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test throughput(ps.lhcopn-ps.surfsara.nl->152.84.101.142), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.2018/01/15 12:30:39 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test throughput(ps.lhcopn-ps.surfsara
.nl->2804:1f10:8000:801::142): 400 BAD REQUEST: Neither the source nor destination is running pScheduler.

2018/01/15 13:29:54 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(marperf01.in2p3.fr->ps02.cat.cbpf.br), continuing with rest of config: 500 timeout
: 500 timeout

2018/01/15 13:29:54 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(ps02.cat.cbpf.br->perfsonar-ps.cnaf.infn.it), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/01/15 13:29:54 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(perfsonar-ps.cnaf.infn.it->ps02.cat.cbpf.br), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/01/15 13:29:54 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(ps02.cat.cbpf.br->ps.lhcopn-ps.surfsara.nl), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/01/15 13:29:54 (14128) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(ps.lhcopn-ps.surfsara.nl->ps02.cat.cbpf.br), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/01/15 13:29:54 (14128) INFO> perfsonar_meshconfig_agent:438 main:: - Added 6 new tasks, and deleted 0 old tasks




Archive powered by MHonArc 2.6.19.

Top of Page