Context
-
Version of iperf3: 3.6
-
Hardware: raspberry pi 3 b
-
Operating system (and distribution, if any): Debian Linux (default pi OS)
Bug Report
I’m trying to run iperf3.6 over a 100kbps link to measuer the actual throughput. I’m running it on two pis.
On the server, I run «iperf3 -s —logfile /dev/tty
On the client, I run «iperf3 -c (IPv6 address of peer) -u -b 390k -l 1024 -t 12»
-
Expected Behavior I see 12 reports, one second apart, then the summary
-
Actual Behavior, on the client I see 11 reports, one second apart, then a pause, then iperf3: error — control socket has closed unexpectedly. On the server I see 16 reports one second apart then iperf3: error — select failed: Bad file descriptor
-
Steps to Reproduce: given above
Server side:
Server listening on 5201
Accepted connection from (IP addr), port 56688
[ 6] local (ip addr) port 5201 connected to (ip addr) port 54260
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 6] 0.00-1.00 sec 9.00 KBytes 73.7 Kbits/sec 37.226 ms 0/9 (0%)
[ 6] 1.00-2.00 sec 10.0 KBytes 81.9 Kbits/sec 55.150 ms 0/10 (0%)
[ 6] 2.00-3.00 sec 11.0 KBytes 90.1 Kbits/sec 65.500 ms 0/11 (0%)
[ 6] 3.00-4.00 sec 9.00 KBytes 73.7 Kbits/sec 72.033 ms 0/9 (0%)
[ 6] 4.00-5.00 sec 11.0 KBytes 90.1 Kbits/sec 73.836 ms 0/11 (0%)
[ 6] 5.00-6.00 sec 10.0 KBytes 81.9 Kbits/sec 74.872 ms 0/10 (0%)
[ 6] 6.00-7.00 sec 11.0 KBytes 90.1 Kbits/sec 74.872 ms 0/11 (0%)
[ 6] 7.00-8.00 sec 10.0 KBytes 81.9 Kbits/sec 75.292 ms 0/10 (0%)
[ 6] 8.00-9.00 sec 10.0 KBytes 81.9 Kbits/sec 75.182 ms 0/10 (0%)
[ 6] 9.00-10.00 sec 11.0 KBytes 90.1 Kbits/sec 75.403 ms 0/11 (0%)
[ 6] 10.00-11.00 sec 10.0 KBytes 81.9 Kbits/sec 89.071 ms 26/36 (72%)
[ 6] 11.00-12.00 sec 10.0 KBytes 81.9 Kbits/sec 53.561 ms 38/48 (79%)
[ 6] 12.00-13.00 sec 10.0 KBytes 81.9 Kbits/sec 36.800 ms 36/46 (78%)
[ 6] 13.00-14.00 sec 10.0 KBytes 81.9 Kbits/sec 25.029 ms 35/45 (78%)
[ 6] 14.00-15.00 sec 11.0 KBytes 90.1 Kbits/sec 17.210 ms 40/51 (78%)
[ 6] 15.00-16.00 sec 10.0 KBytes 81.9 Kbits/sec 13.892 ms 36/46 (78%)
iperf3: error — select failed: Bad file descriptor
Server listening on 5201
Client side:
Connecting to host (IP addr) port 5201
[ 5] local (IP addr) port 54260 connected to (ip addr) port 5201
[ ID] Interval Transfer Bitrate Total Datagrams
[ 5] 0.00-1.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 1.00-2.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 2.00-3.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 3.00-4.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 4.00-5.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 5.00-6.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 6.00-7.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 7.00-8.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 8.00-9.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 9.00-10.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 10.00-11.00 sec 47.0 KBytes 385 Kbits/sec 47
iperf3: error — control socket has closed unexpectedly
This is on a private network that uses valid public network addresses.
Don’t know why part of the output above is in bold.
Problem only occurs with -l 256 and above. Finishes normally with -l 128
What kind of link is it?
I can run just fine using an ODROID-C2. I don’t have an RPI 3B. Amlogic S905 Quad Core Cortex-A53 (ODROID C2) vs Broadcom BCM2837B0 Quad Core Cortex-A53 (RPI). I am running Ubuntu 20.04.1 LTS.
# ./iperf36 --client 192.168.X.X --udp --bandwidth 390k -l 1024
Connecting to host 192.168.X.X, port 5201
[ 5] 0.00-1.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 1.00-2.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 2.00-3.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 3.00-4.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 4.00-5.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 5.00-6.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 6.00-7.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 7.00-8.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 8.00-9.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 9.00-10.00 sec 48.0 KBytes 393 Kbits/sec 48
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-10.00 sec 477 KBytes 391 Kbits/sec 0.000 ms 0/477 (0%) sender
[ 5] 0.00-10.00 sec 477 KBytes 391 Kbits/sec 0.018 ms 0/477 (0%) receiver
iperf Done.
Same for IPv6 …
./iperf36 --client SERVER_IPv6_ADDRESS --udp --bandwidth 390k -l 1024
Connecting to host SERVER_IPv6_ADDRESS, port 5201
[ 5] local CLIENT_IPv6_ADDRESS port 52823 connected to SERVER_IPv6_ADDRESS port 5201
[ ID] Interval Transfer Bitrate Total Datagrams
[ 5] 0.00-1.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 1.00-2.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 2.00-3.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 3.00-4.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 4.00-5.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 5.00-6.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 6.00-7.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 7.00-8.00 sec 47.0 KBytes 385 Kbits/sec 47
[ 5] 8.00-9.00 sec 48.0 KBytes 393 Kbits/sec 48
[ 5] 9.00-10.00 sec 48.0 KBytes 393 Kbits/sec 48
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-10.00 sec 477 KBytes 391 Kbits/sec 0.000 ms 0/477 (0%) sender
[ 5] 0.00-10.00 sec 477 KBytes 391 Kbits/sec 0.019 ms 0/477 (0%) receiver
iperf Done.
Don’t know why part of the output above is in bold
A main issue is that while the client sends about 48KB/sec (390Kbits/sec), the server is receiving only 10KB/sec. It seems that the network throughput is only about 100Kbis/sec. The client probably have a send buffer of about 100KB since the first 100KB were properly received by the server.
After the client completed sending, sending of the 100KB buffered packets continue. This is why the server continue to receive data after the client completed the sending. If my calculations are correct it would take 10 seconds (after the first 12 secs) for the server to receive all buffered data.
Can you send the client and server output when -l 128 was used? In principle it should not change much.
Something happened that that caused the error, I am not sure what, but it may help to try a newer version of iperf3. Version 3.6 is quite old and there were some related fixes since.
Can you try with 3.9? I see this in the release notes for 3.7 …
«The delay for tearing down the control connection for the default timed tests has been increased, to more gracefully handle high-delay paths (#751/#859).»
May be related.
Client is an 1GbE ODROID-C2 running Ubuntu 20.04.1 LTS. Server is a 10GbE rack mount server running Ubuntu 20.04.2 LTS.
I think your link could be causing the issue. Can you provide more details on this 100Kbps link?
# ./iperf36 --client SERVER_IPv4_ADDRESS --udp --bandwidth 390k --time 12 --length 128
Connecting to host SERVER_IPv4_ADDRESS, port 5201
[ 5] local CLIENT_IPv4_ADDRESS port 58317 connected to SERVER_IPv4_ADDRESS port 5201
[ ID] Interval Transfer Bitrate Total Datagrams
[ 5] 0.00-1.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 1.00-2.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 2.00-3.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 3.00-4.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 4.00-5.00 sec 47.5 KBytes 389 Kbits/sec 380
[ 5] 5.00-6.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 6.00-7.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 7.00-8.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 8.00-9.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 9.00-10.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 10.00-11.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 11.00-12.00 sec 47.5 KBytes 389 Kbits/sec 380
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-12.00 sec 571 KBytes 390 Kbits/sec 0.000 ms 0/4570 (0%) sender
[ 5] 0.00-12.03 sec 571 KBytes 389 Kbits/sec 0.042 ms 0/4570 (0%) receiver
# ./iperf36 --server
Server listening on 5201
-----------------------------------------------------------
Accepted connection from CLIENT_IPv4_ADDRESS, port 38364
[ 5] local SERVER_IPv4_ADDRESS port 5201 connected to CLIENT_IPv4_ADDRESS port 58317
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 46.0 KBytes 377 Kbits/sec 0.028 ms 0/368 (0%)
[ 5] 1.00-2.00 sec 47.6 KBytes 390 Kbits/sec 0.038 ms 0/381 (0%)
[ 5] 2.00-3.00 sec 47.6 KBytes 390 Kbits/sec 0.043 ms 0/381 (0%)
[ 5] 3.00-4.00 sec 47.6 KBytes 390 Kbits/sec 0.038 ms 0/381 (0%)
[ 5] 4.00-5.00 sec 47.6 KBytes 390 Kbits/sec 0.043 ms 0/381 (0%)
[ 5] 5.00-6.00 sec 47.6 KBytes 390 Kbits/sec 0.037 ms 0/381 (0%)
[ 5] 6.00-7.00 sec 47.6 KBytes 390 Kbits/sec 0.019 ms 0/381 (0%)
[ 5] 7.00-8.00 sec 47.5 KBytes 389 Kbits/sec 0.035 ms 0/380 (0%)
[ 5] 8.00-9.00 sec 47.6 KBytes 390 Kbits/sec 0.045 ms 0/381 (0%)
[ 5] 9.00-10.00 sec 47.6 KBytes 390 Kbits/sec 0.034 ms 0/381 (0%)
[ 5] 10.00-11.00 sec 47.6 KBytes 390 Kbits/sec 0.036 ms 0/381 (0%)
[ 5] 11.00-12.00 sec 47.6 KBytes 390 Kbits/sec 0.046 ms 0/381 (0%)
[ 5] 12.00-12.03 sec 1.50 KBytes 361 Kbits/sec 0.042 ms 0/12 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-12.03 sec 571 KBytes 389 Kbits/sec 0.042 ms 0/4570 (0%) receiver
# ./iperf36 --client SERVER_IPv6_ADDRESS --udp --bandwidth 390k --time 12 --length 128
Connecting to host SERVER_IPv6_ADDRESS, port 5201
[ 5] local CLIENT_IPv6_ADDRESS port 60491 connected to SERVER_IPv6_ADDRESS port 5201
[ ID] Interval Transfer Bitrate Total Datagrams
[ 5] 0.00-1.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 1.00-2.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 2.00-3.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 3.00-4.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 4.00-5.00 sec 47.5 KBytes 389 Kbits/sec 380
[ 5] 5.00-6.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 6.00-7.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 7.00-8.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 8.00-9.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 9.00-10.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 10.00-11.00 sec 47.6 KBytes 390 Kbits/sec 381
[ 5] 11.00-12.00 sec 47.5 KBytes 389 Kbits/sec 380
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-12.00 sec 571 KBytes 390 Kbits/sec 0.000 ms 0/4570 (0%) sender
[ 5] 0.00-12.04 sec 571 KBytes 389 Kbits/sec 0.014 ms 0/4570 (0%) receiver
# ./iperf36 --server
Server listening on 5201
-----------------------------------------------------------
Accepted connection from CLIENT_IPv6_ADDRESS, port 55168
[ 5] local SERVER_IPv6_ADDRESS port 5201 connected to CLIENT_IPv6_ADDRESS port 60491
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 45.9 KBytes 376 Kbits/sec 0.030 ms 0/367 (0%)
[ 5] 1.00-2.00 sec 47.6 KBytes 390 Kbits/sec 0.015 ms 0/381 (0%)
[ 5] 2.00-3.00 sec 47.6 KBytes 390 Kbits/sec 0.022 ms 0/381 (0%)
[ 5] 3.00-4.00 sec 47.6 KBytes 390 Kbits/sec 0.031 ms 0/381 (0%)
[ 5] 4.00-5.00 sec 47.6 KBytes 390 Kbits/sec 0.024 ms 0/381 (0%)
[ 5] 5.00-6.00 sec 47.6 KBytes 390 Kbits/sec 0.036 ms 0/381 (0%)
[ 5] 6.00-7.00 sec 47.5 KBytes 389 Kbits/sec 0.030 ms 0/380 (0%)
[ 5] 7.00-8.00 sec 47.6 KBytes 390 Kbits/sec 0.025 ms 0/381 (0%)
[ 5] 8.00-9.00 sec 47.6 KBytes 390 Kbits/sec 0.034 ms 0/381 (0%)
[ 5] 9.00-10.00 sec 47.6 KBytes 390 Kbits/sec 0.014 ms 0/381 (0%)
[ 5] 10.00-11.00 sec 47.6 KBytes 390 Kbits/sec 0.030 ms 0/381 (0%)
[ 5] 11.00-12.00 sec 47.6 KBytes 390 Kbits/sec 0.030 ms 0/381 (0%)
[ 5] 12.00-12.04 sec 1.62 KBytes 366 Kbits/sec 0.014 ms 0/13 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-12.04 sec 571 KBytes 389 Kbits/sec 0.014 ms 0/4570 (0%) receiver
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Open
jiachenjun opened this issue
Jul 28, 2017
· 17 comments
Comments
NOTE: The iperf3 issue tracker is for registering bugs, enhancement
requests, or submissions of code. It is not a means for asking
questions about building or using iperf3. Those are best directed
towards the iperf3 mailing list at iperf-dev@google-groups.com or
question sites such as Stack Overflow
(http://www.stackoverflow.com/). A list of frequently-asked questions
regarding iperf3 can be found at http://software.es.net/iperf/faq.html.
Context
-
Version of iperf3:
iperf 3.1.7 -
Hardware:
VM for linux 64bit kernel version 4.4.70 -
Operating system (and distribution, if any):
LFS
Please note: iperf3 is supported on Linux, FreeBSD, and macOS.
Support may be provided on a best-effort basis to other UNIX-like
platforms. We cannot provide support for building and/or running
iperf3 on Windows, iOS, or Android. -
Other relevant information (for example, non-default compilers,
libraries, cross-compiling, etc.):
Please fill out one of the «Bug Report» or «Enhancement Request»
sections, as appropriate.
Bug Report
- Expected Behavior
iperf3 can send sctp traffic successfully. - Actual Behavior
# ./iperf3 -c 192.168.1.7 --sctp -R -b 300M
Connecting to host 192.168.1.7, port 5201
Reverse mode, remote host 192.168.1.7 is sending
[ 4] local 192.168.1.3 port 60663 connected to 192.168.1.7 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 36.4 MBytes 306 Mbits/sec
**iperf3: error - control socket has closed unexpectedly**
- Steps to Reproduce
create sever in one VM with./iperf3 -s 192.168.1.7
start send traffic on another VM with./iperf3 -c 192.168.1.7 --sctp - Possible Solution
N/A
Please submit patches or code changes as a pull request.
Enhancement Request
-
Current behavior
-
Desired behavior
-
Implementation notes
If submitting a proposed implementation of an enhancement request,
please use the pull request mechanism.
EDIT: Do some MarkDown for legibility. —bmah
I download iperf3.2 and try again, same issue still existed.
#./iperf3 -v
iperf 3.2 (cJSON 1.5.2)
Linux 4.4.70-pc64 #1 SMP Mon Jun 26 18:34:34 UTC 2017 x86_64
Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication
#./iperf3 -c 192.168.1.7 -p 10001 --sctp
Connecting to host 192.168.1.7, port 10001
[ 5] local 192.168.1.3 port 59847 connected to 192.168.1.7 port 10001
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 200 MBytes 1.68 Gbits/sec
iperf3: error - unable to write to stream socket: Connection reset by peer
EDIT: MarkDown for legibility. —bmah
I agree it shouldn’t do that. Can you show server-side output as well?
bmah888
changed the title
iperf3 issue:»iperf3: error — control socket has closed unexpectedly»
SCTP test produces «iperf3: error — control socket has closed unexpectedly»
Aug 1, 2017
No feedback after 2.5 months, and I can’t reproduce this with tip of master branch code running on CentOS 7. Closing for now, I can reopen this issue later if necessary.
hi. I am testing this on 3G with udp — packet length 1448B for a 30 second interval. using iperf 3.5 unable to go beyond 28 seconds.
pushing 3 Mbps upstream towards a server
Server output comes as » iperf3 : error — select failed : Bad file descripter.
Hi All
I have figured out that iperf 3.5 fixes this. I actually had iperf 3.4 there. issue is resolved in iperf 3.5
Hi All,
How to install iperf 3.5 in linux?
you can download source code, and upload to VM where you want to use it.
compile & install in vm directly.
Something like:
mkdir iperf3
cd iperf3
tar -xf ../iperf3.5.tar
cd iperf3
./configure
make && make install
From: Shruti Hegde <notifications@github.com>
Sent: Monday, November 5, 2018 3:25 PM
To: esnet/iperf <iperf@noreply.github.com>
Cc: Jia, Chen Jun (NSB — CN/Hangzhou) <chen_jun.jia@nokia-sbell.com>; Author <author@noreply.github.com>
Subject: Re: [esnet/iperf] SCTP test produces «iperf3: error — control socket has closed unexpectedly» (#620)
Hi All,
How to install iperf 3.5 in linux?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#620 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AUX_NNpEnLLk9EM0uoc4VinD4Jw6OQuuks5ur-fEgaJpZM4OmQM1>.
I get this issue on debian buster x64 with the distribution’s version of iperf3.
Client:
# iperf3 --sctp -b 10m -c 10.99.11.1
Connecting to host 10.99.11.1, port 5201
[ 5] local 10.99.37.240 port 42749 connected to 10.99.11.1 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 1.25 MBytes 10.5 Mbits/sec
[ 5] 1.00-2.00 sec 1.19 MBytes 9.96 Mbits/sec
iperf3: error - control socket has closed unexpectedly
Server:
# /usr/bin/iperf3 -s -d
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
get_parameters:
{
"sctp": true,
"omit": 0,
"time": 10,
"parallel": 1,
"len": 65536,
"bandwidth": 10000000,
"pacing_timer": 1000,
"client_version": "3.6"
}
Accepted connection from 10.99.37.240, port 33444
[ 5] local 10.99.11.1 port 5201 connected to 10.99.37.240 port 33351
interval_len 1.000110 bytes_transferred 1245184
interval forces keep
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 1.19 MBytes 9.96 Mbits/sec
iperf3: error - unable to read from stream socket: Bad file descriptor
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Version output:
# /usr/bin/iperf3 --version
iperf 3.6 (cJSON 1.5.2)
Linux desbuild 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64
Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication
problem persists with iperf3 3.7 built from source
Seeing this intermittently on:
iperf 3.6 (cJSON 1.5.2)
Linux 3efa7a0b256a 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64
Optional features available: CPU affinity setting, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing
I’m affected by this as well, please reopen this issue ticket if there isn’t a more suitable one. @bmah888
$ iperf3 -c 192.168.2.1 -p 4711
iperf3: error - control socket has closed unexpectedly
The issue happens immediately, it doesn’t seem like there is any data transferred at all.
$ iperf3 -c 192.168.2.1 -p 4711 -n 100M -v
iperf 3.7 (cJSON 1.5.2)
Linux ThinkPad-X1 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64
Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication
I’m still not able to reproduce this issue, but I believe y’all. Reopening.
Is it possible that those of you with this problem are having some firewall-related issue? That’s a fairly common issue with iperf3 in general.
Thanks for your reply. This is happening inside my local network at home where I have no firewall restrictions at all in place. Is there any way I could give you more information like by adding a very verbose debugging mode? Also, is it possible to query the version of the distant iperf3 server over the wire? I’m experimenting with two Ubuntu servers running iperf3 and there the issue happens only rarely. However, when using my router as server (which has an iperf3 server builtin as well, according to the docs), I always get this message very early on or even before the transfer starts at all.
Thanks for your reply. This is happening inside my local network at home where I have no firewall restrictions at all in place. Is there any way I could give you more information like by adding a very verbose debugging mode? Also, is it possible to query the version of the distant
iperf3server over the wire? I’m experimenting with two Ubuntu servers runningiperf3and there the issue happens only rarely. However, when using my router as server (which has aniperf3server builtin as well, according to the docs), I always get this message very early on or even before the transfer starts at all.
Well, «firewall» could also mean a host-based firewall like iptables or firewalld. But it looks like if you’re doing this between two Ubuntu servers and you get the issue some of the time but not always, that doesn’t really indicate a firewall/packet filtering issue.
There’s a --debug flag in iperf3. If you can run that on the iperf3 server side that might help us a bit. I wonder if having a packet trace (such as from tcpdump) might be helpful.
The server knows the version of the client but not vice versa.
This is a bit of a mystery to me because I have absolutely no idea what’s going wrong.
Er, wait a second @DL6ER . Are you trying this with SCTP (as per the original bug report) or is this with TCP (which is what your command lines indicate)?
I have an observation. I’m using v3.1.3, but this is also repeatable using 3.2 and 3.7.
Using the -A option is breaking iperf and resulting in «control socket has closed unexpectedly». Removing the -A option fixes it.
#iperf3 -c 192.168.1.19 -p 5010 -A 1,3
Connecting to host 192.168.1.19, port 5010
[ 4] local 192.168.1.9 port 54258 connected to 192.168.1.19 port 5010
iperf3: error — control socket has closed unexpectedly
iperf3 -c 192.168.1.19 -p 5010
Connecting to host 192.168.1.19, port 5010
[ 4] local 192.168.1.9 port 54262 connected to 192.168.1.19 port 5010
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 19.0 MBytes 159 Mbits/sec 0 423 KBytes
[ 4] 1.00-2.00 sec 20.1 MBytes 168 Mbits/sec 0 423 KBytes
[ 4] 2.00-3.00 sec 19.1 MBytes 160 Mbits/sec 0 427 KBytes
[ 4] 3.00-4.00 sec 20.6 MBytes 173 Mbits/sec 0 427 KBytes
[ 4] 4.00-5.00 sec 20.6 MBytes 173 Mbits/sec 0 427 KBytes
[ 4] 5.00-6.00 sec 20.9 MBytes 175 Mbits/sec 0 427 KBytes
[ 4] 6.00-7.00 sec 18.8 MBytes 158 Mbits/sec 0 427 KBytes
[ 4] 7.00-8.00 sec 21.0 MBytes 176 Mbits/sec 0 427 KBytes
[ 4] 8.00-9.00 sec 19.6 MBytes 165 Mbits/sec 0 427 KBytes
[ 4] 9.00-10.00 sec 19.6 MBytes 165 Mbits/sec 0 427 KBytes
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 199 MBytes 167 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 197 MBytes 165 Mbits/sec receiver
iperf Done.
trying a quick experiment with ACI to see if I can use it to host iperf3 for some on demand network performance testing. The docker image is https://hub.docker.com/r/netgio/iperf3server/
I can get the container up and running but when I try to connect to it the iperf client gives me the error «iperf3: error — control socket has closed unexpectedly»
I was hoping this would be a simple, single port, single instance use case. are there any specifics related to socket connectivity into ACI instances that would affect this?
EDIT:
iPerf3 defaults to TCP port 5201 so to ensure ACI port mappings are working as expected I created an nginx docker image configured to listen on port 5201 and deployed to ACI. This worked as expected (I could access the default home page at http://:5201). So the issue seems to be specific to whatever iPerf3 is doing with its sockets.
Note the error happens almost immediately at launch of the client iperf3 process.
Hi, Using iperf3 (3.1.3) on Centos 7 (server and client). When performing reverse UDP tests I am seeing intermittent failures. The client fails with: iperf3: error - control socket has closed unexpectedly On the server I see: iperf3: error - unable to write to stream socket: Message too long My client command is: iperf3 -c <host> -p 5207 -u -b 3M -R And server is running with: iperf3 -s -p 5207 -1 --logfile /var/log/iperf3/iperf3-5207.log So far I can only re-create the failure using reverse mode, never in forward mode. Any suggestions? Thanks, Alan
lbaas-iperf3 traffic was stopped after sending traffic about 10-15s
Bug #1498477 reported by
spark
on 2015-09-22
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
|
neutron
|
Expired |
Undecided |
Unassigned
|
Bug Description
iperf3 traffic was stoped after send traffice about 10-15s
root@instance-00000002:/# iperf3 -c 20.1.1.100 -t 1000 -i 1 -p 5001
Connecting to host 20.1.1.100, port 5001
[ 4] local 20.1.1.200 port 59473 connected to 20.1.1.100 port 5001
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 102 MBytes 852 Mbits/sec 36 469 KBytes
[ 4] 1.00-2.00 sec 101 MBytes 849 Mbits/sec 0 547 KBytes
[ 4] 2.00-3.00 sec 100 MBytes 839 Mbits/sec 0 614 KBytes
[ 4] 3.00-4.00 sec 101 MBytes 850 Mbits/sec 3 475 KBytes
[ 4] 4.00-5.00 sec 98.8 MBytes 828 Mbits/sec 0 546 KBytes
[ 4] 5.00-6.00 sec 97.5 MBytes 817 Mbits/sec 0 609 KBytes
[ 4] 6.00-7.00 sec 97.4 MBytes 818 Mbits/sec 1 202 KBytes
[ 4] 7.00-8.00 sec 100 MBytes 839 Mbits/sec 0 346 KBytes
[ 4] 8.00-9.00 sec 98.8 MBytes 828 Mbits/sec 0 440 KBytes
[ 4] 9.00-10.00 sec 96.2 MBytes 808 Mbits/sec 0 515 KBytes
[ 4] 10.00-11.00 sec 97.5 MBytes 818 Mbits/sec 0 580 KBytes
[ 4] 11.00-12.00 sec 97.5 MBytes 817 Mbits/sec 1 136 KBytes
[ 4] 12.00-13.00 sec 100 MBytes 840 Mbits/sec 0 311 KBytes
[ 4] 13.00-14.00 sec 101 MBytes 848 Mbits/sec 0 416 KBytes
[ 4] 14.00-15.00 sec 100 MBytes 841 Mbits/sec 0 502 KBytes
[ 4] 15.00-16.00 sec 100 MBytes 839 Mbits/sec 0 573 KBytes
[ 4] 16.00-17.00 sec 100 MBytes 839 Mbits/sec 0 636 KBytes
[ 4] 17.00-18.00 sec 97.5 MBytes 818 Mbits/sec 0 689 KBytes
[ 4] 18.00-19.00 sec 97.5 MBytes 818 Mbits/sec 11 501 KBytes
[ 4] 19.00-20.00 sec 97.5 MBytes 818 Mbits/sec 0 563 KBytes
[ 4] 20.00-21.00 sec 96.2 MBytes 807 Mbits/sec 0 622 KBytes
[ 4] 21.00-22.00 sec 96.2 MBytes 808 Mbits/sec 0 673 KBytes
[ 4] 22.00-23.00 sec 97.5 MBytes 818 Mbits/sec 0 724 KBytes
[ 4] 23.00-24.00 sec 97.5 MBytes 818 Mbits/sec 0 772 KBytes
[ 4] 24.00-25.00 sec 98.8 MBytes 828 Mbits/sec 10 314 KBytes
[ 4] 25.00-26.00 sec 101 MBytes 849 Mbits/sec 0 421 KBytes
[ 4] 26.00-27.00 sec 100 MBytes 839 Mbits/sec 0 503 KBytes
[ 4] 27.00-28.00 sec 101 MBytes 849 Mbits/sec 0 577 KBytes
[ 4] 28.00-29.00 sec 100 MBytes 839 Mbits/sec 41 436 KBytes
[ 4] 29.00-30.00 sec 101 MBytes 848 Mbits/sec 0 518 KBytes
[ 4] 30.00-31.00 sec 98.8 MBytes 830 Mbits/sec 0 585 KBytes
[ 4] 31.00-32.00 sec 97.5 MBytes 818 Mbits/sec 0 643 KBytes
[ 4] 32.00-33.00 sec 97.5 MBytes 818 Mbits/sec 0 694 KBytes
[ 4] 33.00-34.00 sec 97.5 MBytes 816 Mbits/sec 0 742 KBytes
[ 4] 34.00-35.00 sec 96.2 MBytes 809 Mbits/sec 0 788 KBytes
[ 4] 35.00-36.00 sec 98.8 MBytes 828 Mbits/sec 0 830 KBytes
[ 4] 36.00-37.00 sec 98.7 MBytes 829 Mbits/sec 2 269 KBytes
[ 4] 37.00-38.00 sec 100 MBytes 839 Mbits/sec 0 385 KBytes
[ 4] 38.00-39.00 sec 101 MBytes 848 Mbits/sec 0 477 KBytes
[ 4] 39.00-40.00 sec 100 MBytes 840 Mbits/sec 0 551 KBytes
[ 4] 40.00-41.00 sec 100 MBytes 839 Mbits/sec 0 619 KBytes
[ 4] 41.00-42.00 sec 101 MBytes 848 Mbits/sec 43 344 KBytes
[ 4] 42.00-43.00 sec 100 MBytes 841 Mbits/sec 0 441 KBytes
[ 4] 43.00-44.00 sec 100 MBytes 839 Mbits/sec 0 522 KBytes
[ 4] 44.00-45.00 sec 101 MBytes 849 Mbits/sec 0 592 KBytes
[ 4] 45.00-46.00 sec 100 MBytes 839 Mbits/sec 0 655 KBytes
[ 4] 46.00-47.00 sec 100 MBytes 839 Mbits/sec 4 527 KBytes
[ 4] 47.00-48.00 sec 97.5 MBytes 818 Mbits/sec 0 592 KBytes
[ 4] 48.00-49.00 sec 98.8 MBytes 828 Mbits/sec 2 461 KBytes
[ 4] 49.00-50.00 sec 97.5 MBytes 818 Mbits/sec 0 530 KBytes
iperf3: error — control socket has closed unexpectedly<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<