Skip to Content.
Sympa Menu

perfsonar-user - RE: [perfsonar-user] Unable to use updated iperf3

Subject: perfSONAR User Q&A and Other Discussion

List archive

RE: [perfsonar-user] Unable to use updated iperf3


Chronological Thread 
    < Chronological >      < Thread >
  • From: Ignacio Peluaga Lozada <>
  • To: Mark Feit <>, "" <>
  • Subject: RE: [perfsonar-user] Unable to use updated iperf3
  • Date: Tue, 27 Apr 2021 14:47:28 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 188.184.36.48) smtp.rcpttodomain=internet2.edu smtp.mailfrom=cern.ch; dmarc=bestguesspass action=none header.from=cern.ch; dkim=none (message not signed); arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Cm2QR9J6CY6YyGE4Fmooe2Kdu7rdJCGGruwz7q4aD5o=; b=gC6RQVqDU7bmUUYBamyILD3MfKpG6RRgO3jX80bVG4qXPqItyXBtiF5LeOP7GSi91ntttq7yKJgZH7MkhtrVNcP1tcL/5iwrRW3LMPh+Tg7q43M4aK8RVk8mUI8bCWbbM6lFh2EpmNMXygUzjrwsljIcTkt9a/KbKJncqApCBrLkA6qVOxnd/PbQn+uezfeazrlN+8sa8Sbl9ibrEJfe6EeNxjVgEFyoKrwkk2zHc10AG0z/DXhjF1jY+xfeA9iZt7Uyy/F1J8PNBpD4prgP9S2iTJN5AwkGW6QuUBvkK0ddvjIvQdYgYgC9SdjO7zxiEp9196KvmcYHKgpgUORuIw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EB5Z2Kt6iJs3vfGIjaBLIsJOSiQ+J7vd1kvi17dgpdnsEjNex1W4iZ3RB4DGqpbleQXlI+phD4EwSxfr/s6GVWm3HRODxLLM8ug9yqqfpRT1Rh12gCKRCmn0B7u2DLuaHHYBX0dtggQ/3oqlkCBXdIJDcIK4pvG+H16MTnVdJ2mPzzdYnBhqTr8ycdPGdkCWqVfsETDdNhnWBk+I0JhruvhwOHIUzsmDkkvxwukN3kSht1otJ0D+ow+SI0u4iXXEk9G3QQ0HQW9nphJ4ilwYNgKId9iN2ji2YlDFh+8SYULejEidHH1x+MeJPErmICCMJnxNJ5hPhafN9IqxUwfmtA==
Hi Mark,

great, thanks for the details. I managed to fix it installing
pscheduler-tool-iperf3.

In any case, automatic updates are enabled ('enabled' set to 1 in
/etc/yum.repos.d/perfSONAR.repo) and in fact the toolkit's GUI shows
everything is version 4.3.4-1.el7.
Then, shouldn't these updates also take care of the underlying iperf3?

Thanks again Mark.

Regards,
Ignacio

________________________________________
From: Mark Feit []
Sent: 26 April 2021 23:40
To: Ignacio Peluaga Lozada;
Subject: Re: Unable to use updated iperf3

Ignacio Peluaga Lozada writes:

I have a perfSONAR toolkit which had iperf 3.1.7 and I updated it manually to
3.9 (uninstalled 3.1.7, then downloaded 3.9 from
https://downloads.es.net/pub/iperf/).

3.1.7 was a documentation-fixes-only release that was never shipped with the
toolkit and is also four years old. All versions of the toolkit that had
iperf3 3.1.x are well past end of life and are no longer supported. Any
toolkit that has been consistently upgraded to the latest should already be
running 3.9. We recommend doing regular updates for new features and
security fixes.

I can run iperf3 on that server (located at /usr/bin/ with the same
permissions other tools like traceroute, nuttcp, etc have) but pScheduler
doesn't seem to find it. When I run a throughput test with '--tool iperf3',
for example: … "pscheduler task --tool iperf3 throughput --dest
psb01-gva.cern.ch" … I get: … "Failed to post task: Unable to complete
request: No tool in common among the participants: localhost offered nuttcp,
iperf2, ethr; psb01-gva.cern.ch offered iperf3, nuttcp, iperf2, ethr."

The package pscheduler-tool-iperf3 depends on iperf3. If you allowed the
package manager to remove dependencies when you uninstalled iperf3, that
package and all of pScheduler’s understanding of iperf3 were uninstalled with
it.

Also, we don’t recommend running the “pscheduler internal” family of commands
unless advised by the development team. Nothing you tried was harmful, but
there are a few very pointy things in that drawer.

--Mark


Archive powered by MHonArc 2.6.24.

Top of Page