perfsonar-user - Re: [perfsonar-user] pScheduler ping localhost failed
Please Wait...
perfsonar-user@internet2.edu
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Mark Feit <mfeit@internet2.edu>
- To: Tao Zhang <Tao.Zhang@canarie.ca>, Szymon Trocha <szymon.trocha@man.poznan.pl>, David Szydloski <dszydloski@vidscale.com>
- Cc: "perfsonar-user@internet2.edu" <perfsonar-user@internet2.edu>
- Subject: Re: [perfsonar-user] pScheduler ping localhost failed
- Date: Wed, 28 Mar 2018 14:45:22 +0000
- Accept-language: en-US
- Authentication-results: canarie.ca; dkim=none (message not signed) header.d=none;canarie.ca; dmarc=none action=none header.from=internet2.edu;
- Ironport-phdr: 9a23:KT33tR8yaxnQMP9uRHKM819IXTAuvvDOBiVQ1KB+0+wSIJqq85mqBkHD//Il1AaPAd2Araocw8Pt8InYEVQa5piAtH1QOLdtbDQizfssogo7HcSeAlf6JvO5JwYzHcBFSUM3tyrjaRsdF8nxfUDdrWOv5jAOBBr/KRB1JuPoEYLOksi7ze+/94HdbglSmDaxfa55IQmrownWqsQYm5ZpJLwryhvOrHtIeuBWyn1tKFmOgRvy5dq+8YB6/ShItP0v68BPUaPhf6QlVrNYFygpM3o05MLwqxbOSxaE62YGXWUXlhpIBBXF7A3/U5zsvCb2qvZx1S+HNsHwU700Xi6t77x3SBDyjCcMKjo1/W/LhsBsia5Wpg+qqR5izI7OeIybNORwcL7Bfd0URmRBUMReVy1dDYyzdIYAFfYNPeNCooXhu1cDrx2zDhSsCuP1zT9Ig2f706og3OQ7EgHNwQwuEMwPsHTIsd74M6ISUe6rw6nJ0TXOdPJW2THh6IfWaBAhp++DXa5ufcbL10YgCh7Fg0yWpIf4MT2V0eENvHKa7+pmTe+glXUnpxt3ojex2scgkpfFip4Vx1ze6Cl0w4I4Kce2RUJle9KoDphduieHPIV1WsMvW39ktzwmxrEbvJO3YTUGxIkiyh7RZPGLb5SE7xfhWemPLjp0mXdodbehixqu70Ss0vDwWtW33VpQsCZIkcPAum4C2hHX8MSLV+Zx8lq51TaByQ/e6f1ILEUxmKbFL5Mu3KM8m58OvUTNESL6hkD7gauYe0gl5+el7uTqYrv4qpCHMYJ/lxvwPb40msOlBOQ1KggOUHaf+eS7zLDt5VH0TrJWgvEri6XUrYjUKMoCqq6+GABazJwv6xGiDze6y9sYmmQHLFRYdx6dl4jpIVbOIOzmAvijn1SskTBrx/bcMr3mH5XNMnzDkLDmfbZ+8UJT1A0zzdVH65JVDLEOPu7zV1fvuNPCEhM1Lgm5z/v6BNlg044eV22CDrOFPK7Xs1KH+O0iL/SJaYIQpjrxN+Yp6+brjXAjmF8deaep3YEQaHC9BvlmJkuZbmTtgtcdCmoKvww+TPD0h12YVz5ceWqyU7wm6j4lFY2mEJ/PRpqxj7yZwCe7AppWa3heCl+SC3foeZ6EW/AKaC2IOM9tiyEEVaO/RI87zhyusA76y6F7LurP5CEUr5Pj1N5p5+LNjxEy8yJ7D9iD322XUW57g34IFHcK2/VDqEs1+FeK16cw18BREpph5/pPXS8xPJjV1e13Tdv7DEaJRcWYTVGgCum8BjoxR5pl2M0fZkF7Xcm4iRvD1gKvCrlTj7uZApUytLrYiTy5C89jynqO77swg10hWchOfTmqnbxu+wzUHI3Iu1uYm72hfKARmiXK8THQ43CJuRR9WRRzGYvIXGxXMk7YoNXlzkLEU7K0D7k7aE1MxdPUefgCUcHgkVgTHaSrA9/ZeW/kwD/oCA==
- Spamdiagnosticoutput: 1:0
Tao Zhang writes: The thoughput result also looks fine, however, I need to wait about 3 minutes for the result bwctl -T iperf3 -s 198.165.161.174 -c 205.189.32.28 -t 30 -i 1 -f m -O 3 The use of bwctl as a command-line tool has been deprecated since we released 4.0 last April. The system has provisions for backward
compatibility to ease the transition to pScheduler, but those will be going away after we release 4.1. Using the pScheduler CLI to test throughput between those hosts works just fine: $ pscheduler task throughput --source 205.189.32.28 --dest 198.165.161.174 Submitting task... Task URL: https://205.189.32.28/pscheduler/tasks/4a94d7e0-2d38-4183-8008-4a2794896a93 Running with tool 'iperf3' Fetching first run... Next scheduled run: https://205.189.32.28/pscheduler/tasks/4a94d7e0-2d38-4183-8008-4a2794896a93/runs/7f433f1f-3c63-442c-9f79-81f15f4ec633 Starts 2018-03-28T12:42:25Z (~6 seconds) Ends 2018-03-28T12:42:44Z (~18 seconds) Waiting for result... * Stream ID 5 Interval Throughput Retransmits Current Window
0.0 - 1.0 935.56 Mbps 0 8.56 MBytes
1.0 - 2.0 943.74 Mbps 0 8.56 MBytes
2.0 - 3.0 943.72 Mbps 0 8.56 MBytes
3.0 - 4.0 943.60 Mbps 0 8.56 MBytes
4.0 - 5.0 933.32 Mbps 0 8.56 MBytes
5.0 - 6.0 943.74 Mbps 0 8.62 MBytes
6.0 - 7.0 954.19 Mbps 0 9.06 MBytes
7.0 - 8.0 943.72 Mbps 0 9.06 MBytes
8.0 - 9.0 943.72 Mbps 0 9.06 MBytes
9.0 - 10.0 933.21 Mbps 0 9.06 MBytes
Summary Interval Throughput Retransmits
0.0 - 10.0 941.85 Mbps 0 No further runs scheduled. ESNet has a good summary of how to use the pScheduler CLI and equivalent commands for old favorites:
https://fasterdata.es.net/performance-testing/network-troubleshooting-tools/pscheduler/ the owping test is more problematic.
1)
owping the box itself owping 198.165.161.174 Approximately -232.8 seconds until results available I just tried the same thing (which is fine because all perSONAR boxes run an OWAMP daemon) and owping seems to be getting caught
up doing something DNS-related. Trying to do any basic DNS lookups (dig, nslookup) on that host doesn’t go well, either, so the cause of that might be related to how that’s configured. Owping to the other machine (205.189.32.28)
works fine, so I suspect you have a network or DNS configuration problem. --Mark |
- [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, David Szydloski, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Szymon Trocha, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Mark Feit, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Michael Johnson, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Mark Feit, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/28/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Mark Feit, 03/28/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Michael Johnson, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, David Szydloski, 03/26/2018
Archive powered by MHonArc 2.6.19.