From: dignacioconde <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] [tohojo/flent] No suitable Iperf binary Found (#171)
Date: Tue, 23 Jul 2019 13:39:59 -0700 [thread overview]
Message-ID: <tohojo/flent/issues/171@github.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1847 bytes --]
root@n1:/tmp/pycore.50542/n1.conf# flent -H 10.0.0.21 udp_flood --debug-error
Started Flent 1.3.0 using Python 3.6.8.
Starting udp_flood test. Expected run time: 70 seconds.
WARNING: Found iperf binary (), but it does not have an --enhancedreports option. Not using.
ERROR: Runner UDP upload failed check: No suitable Iperf binary found.
Traceback (most recent call last):
File "/usr/share/flent/flent/aggregators.py", line 121, in collect
t.check()
File "/usr/share/flent/flent/runners.py", line 1457, in check
marking=self.marking)
File "/usr/share/flent/flent/runners.py", line 1503, in find_binary
raise RunnerCheckError("No suitable Iperf binary found.")
flent.runners.RunnerCheckError: No suitable Iperf binary found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/flent/flent/__init__.py", line 59, in run_flent
b.run()
File "/usr/share/flent/flent/batch.py", line 617, in run
return self.run_test(self.settings, self.settings.DATA_DIR, True)
File "/usr/share/flent/flent/batch.py", line 515, in run_test
res = self.agg.postprocess(self.agg.aggregate(res))
File "/usr/share/flent/flent/aggregators.py", line 233, in aggregate
measurements, metadata, raw_values = self.collect()
File "/usr/share/flent/flent/aggregators.py", line 123, in collect
raise RuntimeError("Runner %s failed check: %s" % (n, e))
RuntimeError: Runner UDP upload failed check: No suitable Iperf binary found.
I though it was because of the binary name, it was iperf3 so i renamed it to iperf but it seems Flent needs iperf 2? It's the one that has --enhancedreports option.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/171
[-- Attachment #1.2: Type: text/html, Size: 3191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
next reply other threads:[~2019-07-23 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 20:39 dignacioconde [this message]
2019-07-23 21:07 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tohojo/flent/issues/171@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJPY7FYS7CMHTD4UZC6N3ISRR7EVBNHHBYII2TE@reply.github.com \
--cc=subscribed@noreply.github.com \
--subject='Re: [Flent-users] [tohojo/flent] No suitable Iperf binary Found (#171)' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox