Flent-users discussion archives
 help / color / mirror / Atom feed
From: Jonas Smedegaard <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] support (re-)enabling netperf routing of UDP packets (#214)
Date: Fri, 04 Dec 2020 12:25:59 -0800	[thread overview]
Message-ID: <tohojo/flent/issues/214/739000950@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/214@github.com>

[-- Attachment #1: Type: text/plain, Size: 6228 bytes --]

Sorry, I was too quick to conclude the exact cause of error messages I saw in the GUI.

When I saw those errors I cancelled the test, expecting no results at all - but trying more patiently to let it run its course I now see that output is generate (so something works) and those error messages are nicely emitted on console too (not only in GUI window), along with more details:
```
$ flent-gui 
Started Flent 1.3.2 using Python 3.9.1rc1.
Initialised matplotlib v3.3.2 on numpy v1.19.4.
GUI loaded. Running on PyQt v5.15.2.
Starting rrul test. Expected run time: 70 seconds.
WARNING: Program exited non-zero.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4 -Y EF,EF -H XXXXX -p 12865 -t UDP_RR -l 70 -F /dev/urandom    -- -e 2  -H XXXXX -k THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD  
Return code: 1
Stdout: send_data: data send error: Invalid argument (errno 22)

Stderr: netperf: send_omni: send_data failed: Invalid argument

WARNING: Command produced no valid data.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4 -Y EF,EF -H XXXXX -p 12865 -t UDP_RR -l 70 -F /dev/urandom    -- -e 2  -H XXXXX -k THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD  
Return code: 1
Stdout: send_data: data send error: Invalid argument (errno 22)

Stderr: netperf: send_omni: send_data failed: Invalid argument

WARNING: Program exited non-zero.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4 -Y CS1,CS1 -H XXXXX -p 12865 -t UDP_RR -l 70 -F /dev/urandom    -- -e 2  -H XXXXX -k THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD  
Return code: 1
Stdout: send_data: data send error: Invalid argument (errno 22)

Stderr: netperf: send_omni: send_data failed: Invalid argument

WARNING: Command produced no valid data.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4 -Y CS1,CS1 -H XXXXX -p 12865 -t UDP_RR -l 70 -F /dev/urandom    -- -e 2  -H XXXXX -k THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD  
Return code: 1
Stdout: send_data: data send error: Invalid argument (errno 22)

Stderr: netperf: send_omni: send_data failed: Invalid argument

WARNING: Program exited non-zero.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4  -H XXXXX -p 12865 -t UDP_RR -l 70 -F /dev/urandom    -- -e 2  -H XXXXX -k THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD  
Return code: 1
Stdout: send_data: data send error: Invalid argument (errno 22)

Stderr: netperf: send_omni: send_data failed: Invalid argument

WARNING: Command produced no valid data.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4  -H XXXXX -p 12865 -t UDP_RR -l 70 -F /dev/urandom    -- -e 2  -H XXXXX -k THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD  
Return code: 1
Stdout: send_data: data send error: Invalid argument (errno 22)

Stderr: netperf: send_omni: send_data failed: Invalid argument


Summary of rrul test run from 2020-12-04 20:04:49.807272

                             avg       median          # data pts
 Ping (ms) ICMP   :        40.35        41.60 ms              350
 Ping (ms) UDP BE : No data.
 Ping (ms) UDP BK : No data.
 Ping (ms) UDP EF : No data.
 Ping (ms) avg    :        40.35          N/A ms              350
 TCP download BE  :         0.82         0.77 Mbits/s         350
 TCP download BK  :         0.80         0.75 Mbits/s         350
 TCP download CS5 :         0.79         0.75 Mbits/s         350
 TCP download EF  :         0.67         0.63 Mbits/s         350
 TCP download avg :         0.77          N/A Mbits/s         350
 TCP download sum :         3.08          N/A Mbits/s         350
 TCP totals       :        94.35          N/A Mbits/s         350
 TCP upload BE    :        23.03        23.02 Mbits/s         350
 TCP upload BK    :        22.70        22.67 Mbits/s         350
 TCP upload CS5   :        22.87        22.91 Mbits/s         350
 TCP upload EF    :        22.67        23.21 Mbits/s         350
 TCP upload avg   :        22.82          N/A Mbits/s         350
 TCP upload sum   :        91.27          N/A Mbits/s         350
Data file written to /home/jonas/flent/rrul-2020-12-04T210449.807272.flent.gz.
```

Output graph for an RRUL test is missing the 3 UDP ping series, but all other series seem to have gotten through.  Perhaps this is no issue in flent after all, just my cloud provider blocking UDP ping...

-- 
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/214#issuecomment-739000950

[-- Attachment #2: Type: text/html, Size: 7158 bytes --]

  parent reply	other threads:[~2020-12-04 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 10:19 [Flent-users] " Jonas Smedegaard
2020-12-04 12:35 ` [Flent-users] " Toke Høiland-Jørgensen
2020-12-04 20:25 ` Jonas Smedegaard [this message]
2020-12-06 12:03 ` Toke Høiland-Jørgensen
2020-12-06 12:56 ` Jonas Smedegaard
2020-12-08 16:19 ` Toke Høiland-Jørgensen
2020-12-08 16:54 ` Jonas Smedegaard
2020-12-08 21:12 ` Toke Høiland-Jørgensen
2020-12-08 21:12 ` 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/214/739000950@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP57BJISHZUUQOMVDT552Z6FPEVBNHHC2HVG4M@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='[Flent-users] Re: [tohojo/flent] support (re-)enabling netperf routing of UDP packets (#214)' \
    /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