Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Regular test with Perfsonar4 and ipv6

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Regular test with Perfsonar4 and ipv6


Chronological Thread 
  • From: Rodrigo Augusto Girani Tejos <>
  • To:
  • Subject: [perfsonar-user] Regular test with Perfsonar4 and ipv6
  • Date: Fri, 15 Sep 2017 15:54:03 -0300 (BRT)
  • Importance: high
  • Ironport-phdr: 9a23:dFzrLxDbEWvlBm9r0f5NUyQJP3N1i/DPJgcQr6AfoPdwSPX9p8bcNUDSrc9gkEXOFd2CrakV26yO6+jJYi8p2d65qncMcZhBBVcuqP49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL1LdrWev4jEMBx7xKRR6JvjvGo7Vks+7y/2+94fdbghMhzexe69+IAmrpgjNq8cahpdvJLwswRXTuHtIfOpWxWJsJV2Nmhv3+9m98p1+/SlOovwt78FPX7n0cKQ+VrxYES8pM3sp683xtBnMVhWA630BWWgLiBVIAgzF7BbnXpfttybxq+Rw1DWGMcDwULs5Xymp4aV2Rx/ykCoJOT43/n/UhMNykaxUrw6uqQZ8zI7VZ4+YL+Bxcr/BctwBX2dNQsRcWipcCY28dYsPCO8BMP5EoYn6ulQOtxq+BQarBOjy1jJIm3D23bAh0+Q9FgHNwQ0uH9MUsHvOqtX1NboZX/6rw6nKyjXDdO5d1DDn6IjUbB8ho/aMXalrfMrV00YvDR/Kgk+NqYz+JzOZzP8Cs3KC4udmSOmhhWknqwRrrTiuwMchkpTJhpkNylze7ip52p45Kse9SE5je9GkDJtQuzucN4RoXsMuW3lotzggyr0Iop67ey4Kx449xxLFbfyIbZSI7gr+WOqPIzp0nm5pdKijixqo7ESs0vPwWtWo3FpQsyZIkMPAum4J2hDJ9MSLVPlw80G80jiMzwDe8v9ILVwomabBNpIszbE9moAOvUnAESL6gkv7gLeLekgr9OWk8fnrbqnkq5OGKoN4lxzyPr4zlsCiD+k0KhYCU3SH9eimybHu8kL0TK9XgvA1jKXVqo7WKdgaq6O/HgRbyJws6wylADejyNkYnWcILFZCeB+fiIjpJ0vOL+r+DfejhFSgiiprx+vePr3nHJrNMmLPkKr6fbZl8UJT0xAzwche55JSFL4BPOr+VlHtuNDEFBM1LgO5zun9BNlg1Y4TVniDD6GBPKPXq1CI5+YvI+eWZI8SvTbwM+Il5+Lwgn87nl8dZrKk3Z8NZ3CiAvtqOViZYWH0gtsbCmgKpBIyTPb2h12aTT5Te3GyUrok5j4lEoKmA5zDRoergLObxie3B4BWZntYBVCWCnroc4SEW+wQaCKJPMNtiD0EVb69S4A/zxGushH1y6Z5IubO5CIXqI/jh5BJ4LjLmAs87jtyBt7YznqAVUl1mH8FXTk7wPo5rEBgmXmZ1q0tuftUD91c4LtgTwgnLoLbh8N7Edn0W0r9c9WOUx7yWMmrAzYqZtY42dRIfl1lXd+42EOQlxG2CqMYwuTYTKc/9bjRiiD8
Hello,

I add a Throughtput TCP IPv6 test via web interface, but the results of this test do not appear in "Test Results".

To try to resolve the issue I look in pscheduler logs ("/var/log/pscheduler/pscheduler.log") and the following result for the ipv6 test was:

Running https://127.0.0.1/pscheduler/tasks/fd59028e-dc59-4ad6-9f98-7368e92d5f09/runs/ec2fbdb7-726b-4869-b9e1-7ed414f2c267
With traceroute: trace --dest ps-bw.l3-santiago.ampath.net --ip-version 6
Run succeeded.
Posted result to https://200.17.29.227/pscheduler/tasks/210c81fd-7f8e-4bda-a00f-768cb6dfdf5c/runs/66bf7717-86cc-46b6-950e-9bb708c1e8f0

The JSON response of the test is:

{
  "result-href": "https://ps-bw.sciencedmz.usp.br/pscheduler/tasks/fd59028e-dc59-4ad6-9f98-7368e92d5f09/runs/be1d88de-6fc2-4fa2-9ac6-d15a98c7a426/result",
  "result-full": [
    {
      "diags": "traceroute -q 1 -6 -N 30 -n ps-bw.l3-santiago.ampath.net",
      "result": null,
      "succeeded": false,
      "error": "ps-bw.l3-santiago.ampath.net: Name or service not known\nCannot handle \"host\" cmdline arg `ps-bw.l3-santiago.ampath.net' on position 1 (argc 7)\n"
    }
  ],
  "end-time": "2017-09-15T18:03:55Z",
  "participant": 0,
  "participant-data": {},
  "result-merged": {
    "succeeded": false,
    "schema": 1
  },
  "participant-data-full": [
    {}
  ],
  "participants": [
    "127.0.0.1"
  ],
  "state-display": "Finished",
  "archivings": [
    {
      "diags": [
        {
          "return-code": 0,
          "time": "2017-09-15T15:03:55-03:00",
          "stderr": "",
          "stdout": {
            "succeeded": true
          }
        }
      ],
      "archived": true,
      "archiver": {
        "schema": 1,
        "version": "1.0",
        "maintainer": {
          "href": "http://www.perfsonar.net",
          "name": "perfSONAR Development Team",
          "email": ""
        },
        "description": "Send results to Esmond",
        "name": "esmond"
      },
      "archiver_data": {
        "url": "https://localhost/esmond/perfsonar/archive/",
        "retry-policy": [
          {
            "attempts": 1,
            "wait": "PT60S"
          },
          {
            "attempts": 1,
            "wait": "PT300S"
          }
        ],
        "_auth-token": null
      },
      "last_attempt": "2017-09-15T18:03:55.838997+00:00"
    }
  ],
  "state": "finished",
  "errors": null,
  "href": "https://ps-bw.sciencedmz.usp.br/pscheduler/tasks/fd59028e-dc59-4ad6-9f98-7368e92d5f09/runs/be1d88de-6fc2-4fa2-9ac6-d15a98c7a426",
  "task-href": "https://ps-bw.sciencedmz.usp.br/pscheduler/tasks/fd59028e-dc59-4ad6-9f98-7368e92d5f09",
  "duration": "P0D",
  "start-time": "2017-09-15T18:03:55Z",
  "added": "2017-09-15T14:24:35Z",
  "result": {
    "diags": "traceroute -q 1 -6 -N 30 -n ps-bw.l3-santiago.ampath.net",
    "result": null,
    "succeeded": false,
    "error": "ps-bw.l3-santiago.ampath.net: Name or service not known\nCannot handle \"host\" cmdline arg `ps-bw.l3-santiago.ampath.net' on position 1 (argc 7)\n"
  }
}

If we look at the above result, there is an error (highlight in red).

I could not find any solutions for this error, could someone advise me how to address this issue?

By the way, when I try a test in CLI mode (pscheduler task throughput --dest 2800:bc0:8000:4002::114
 or pscheduler task trace --dest 2800:bc0:8000:4002::114) it works perfect.


Thanks, 

Rodrigo 



Archive powered by MHonArc 2.6.19.

Top of Page