[perfsonar-user] Unable to use updated iperf3

[Ignacio Peluaga Lozada]

Hi all,

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/).

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."

Without the --tool option it works fine but uses nuttcp. From what I've seen on the logs, a SQL database is queried to check what tools are available on the node.
How can I update that DB? I tried these two but didn't fix the problem:

sudo pscheduler internal db-update
sudo yum reinstall pscheduler-server

Many thanks in advance.

Regards,
Ignacio

[Mark Feit]

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

[Ignacio Peluaga Lozada]

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 [***@internet2.edu]
Sent: 26 April 2021 23:40
To: Ignacio Peluaga Lozada; perfsonar-***@internet2.edu
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