Ubuntu
iperf package

hangs and connection resets w/ high thread count

Bug #1832399 reported by dann frazier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
iperf (Debian)
Fix Released
Unknown
iperf (Ubuntu)
Fix Released
Undecided
dann frazier
Bionic
Fix Released
Undecided
dann frazier
Cosmic
Fix Released
Undecided
dann frazier
Disco
Fix Released
Undecided
dann frazier
Eoan
Fix Released
Undecided
dann frazier

Bug Description

[Impact]
When attempting an iperf run with 24 threads, I either hit a
hang or a bunch of "write failed: Connection reset by peer"
errors. These are both resolved by the following upstream commit:

https://sourceforge.net/p/iperf2/code/ci/4565c2ce318318a8a1d4578bab78c0e03fb49437/

[Test Case]
$ iperf -c 192.168.86.2 -P 24
^C^Cconnect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
^C^C^Z
[1]+ Stopped iperf -c 192.168.86.2 -P 24
$ bg
[1]+ iperf -c 192.168.86.2 -P 24 &
$ killall -9 iperf
$ fg
-bash: fg: job has terminated
[1]+ Killed iperf -c 192.168.86.2 -P 24

$ iperf -c 192.168.86.2 -P 24
------------------------------------------------------------
Client connecting to 192.168.86.2, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
write failed: Connection reset by peer
write failed: Connection reset by peer
write failed: Connection reset by peer
write failed: Connection reset by peer
[ 21] local 192.168.86.1 port 47950 connected with 192.168.86.2 port 5001
[ ID] Interval Transfer Bandwidth
[ 21] 0.0- 0.0 sec 107 KBytes 0.00 bits/sec
[ 16] local 192.168.86.1 port 47940 connected with 192.168.86.2 port 5001
[ 16] 0.0- 0.0 sec 107 KBytes 0.00 bits/sec
[ 4] local 192.168.86.1 port 47914 connected with 192.168.86.2 port 5001
[ 8] local 192.168.86.1 port 47918 connected with 192.168.86.2 port 5001
[ 3] local 192.168.86.1 port 47916 connected with 192.168.86.2 port 5001
[ 5] local 192.168.86.1 port 47920 connected with 192.168.86.2 port 5001
[ 6] local 192.168.86.1 port 47922 connected with 192.168.86.2 port 5001
[ 7] local 192.168.86.1 port 47924 connected with 192.168.86.2 port 5001
[ 22] local 192.168.86.1 port 47952 connected with 192.168.86.2 port 5001
[ 9] local 192.168.86.1 port 47926 connected with 192.168.86.2 port 5001
[ 20] local 192.168.86.1 port 47948 connected with 192.168.86.2 port 5001
[ 26] local 192.168.86.1 port 47960 connected with 192.168.86.2 port 5001
[ 19] local 192.168.86.1 port 47946 connected with 192.168.86.2 port 5001
[ 15] local 192.168.86.1 port 47938 connected with 192.168.86.2 port 5001
[ 15] 0.0- 0.0 sec 107 KBytes 0.00 bits/sec
[ 10] local 192.168.86.1 port 47930 connected with 192.168.86.2 port 5001
[ 25] local 192.168.86.1 port 47958 connected with 192.168.86.2 port 5001
[ 12] local 192.168.86.1 port 47928 connected with 192.168.86.2 port 5001
[ 17] local 192.168.86.1 port 47944 connected with 192.168.86.2 port 5001
[ 14] local 192.168.86.1 port 47936 connected with 192.168.86.2 port 5001
[ 13] local 192.168.86.1 port 47934 connected with 192.168.86.2 port 5001
[ 11] local 192.168.86.1 port 47932 connected with 192.168.86.2 port 5001
[ 11] 0.0- 0.0 sec 107 KBytes 0.00 bits/sec
[ 24] local 192.168.86.1 port 47956 connected with 192.168.86.2 port 5001
[ 23] local 192.168.86.1 port 47954 connected with 192.168.86.2 port 5001
[ 18] local 192.168.86.1 port 47942 connected with 192.168.86.2 port 5001
write failed: Connection reset by peer
write failed: Connection reset by peer
[ 12] 0.0- 0.0 sec 107 KBytes 73.0 Mbits/sec
[ 18] 0.0- 0.0 sec 107 KBytes 73.3 Mbits/sec
[ 4] 0.0-10.0 sec 4.19 GBytes 3.60 Gbits/sec
[ 8] 0.0-10.0 sec 2.87 GBytes 2.47 Gbits/sec
[ 3] 0.0-10.0 sec 2.04 GBytes 1.75 Gbits/sec
[ 5] 0.0-10.0 sec 2.00 GBytes 1.72 Gbits/sec
[ 6] 0.0-10.0 sec 2.71 GBytes 2.33 Gbits/sec
[ 7] 0.0-10.0 sec 4.10 GBytes 3.52 Gbits/sec
[ 22] 0.0-10.0 sec 2.00 GBytes 1.72 Gbits/sec
[ 9] 0.0-10.0 sec 2.71 GBytes 2.33 Gbits/sec
[ 20] 0.0-10.0 sec 2.82 GBytes 2.42 Gbits/sec
[ 26] 0.0-10.0 sec 2.71 GBytes 2.32 Gbits/sec
[ 19] 0.0-10.0 sec 4.58 GBytes 3.94 Gbits/sec
[ 10] 0.0-10.0 sec 2.92 GBytes 2.51 Gbits/sec
[ 25] 0.0-10.0 sec 4.15 GBytes 3.57 Gbits/sec
[ 17] 0.0-10.0 sec 2.74 GBytes 2.35 Gbits/sec
[ 14] 0.0-10.0 sec 2.78 GBytes 2.39 Gbits/sec
[ 13] 0.0-10.0 sec 2.00 GBytes 1.72 Gbits/sec
[ 24] 0.0-10.0 sec 2.81 GBytes 2.41 Gbits/sec
[ 23] 0.0-10.0 sec 4.13 GBytes 3.55 Gbits/sec
[SUM] 0.0-10.0 sec 54.3 GBytes 46.6 Gbits/sec

[Fix]
https://sourceforge.net/p/iperf2/code/ci/4565c2ce318318a8a1d4578bab78c0e03fb49437/

[Regression Risk]
Allowing more connections allows for more consumption of system resources.

Bug Watch Updater (bug-watch-updater)
Changed in iperf (Debian):
status: Unknown → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iperf - 2.0.12+dfsg1-2ubuntu1

---------------
iperf (2.0.12+dfsg1-2ubuntu1) eoan; urgency=medium

  * Add backlog_increase.patch to fix hangs and connection resets
    with high thread count. LP: #1832399.
  * Add signal_bug.patch to fix issue with the server not exiting
    via SIGINT. LP: #1832401.

 -- dann frazier <email address hidden> Thu, 13 Jun 2019 16:34:58 -0600

Changed in iperf (Ubuntu Eoan):
status: New → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in iperf (Debian):
status: Confirmed → Fix Released
dann frazier (dannf)
Changed in iperf (Ubuntu Disco):
status: New → In Progress
Changed in iperf (Ubuntu Eoan):
assignee: nobody → dann frazier (dannf)
Changed in iperf (Ubuntu Disco):
assignee: nobody → dann frazier (dannf)
Changed in iperf (Ubuntu Cosmic):
status: New → In Progress
Changed in iperf (Ubuntu Bionic):
status: New → In Progress
assignee: nobody → dann frazier (dannf)
Changed in iperf (Ubuntu Cosmic):
assignee: nobody → dann frazier (dannf)
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello dann, or anyone else affected,

Accepted iperf into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iperf/2.0.12+dfsg1-2ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in iperf (Ubuntu Disco):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-disco
Changed in iperf (Ubuntu Cosmic):
status: In Progress → Fix Committed
tags: added: verification-needed-cosmic
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello dann, or anyone else affected,

Accepted iperf into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iperf/2.0.10+dfsg1-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in iperf (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed-bionic
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello dann, or anyone else affected,

Accepted iperf into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iperf/2.0.10+dfsg1-1ubuntu0.18.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
dann frazier (dannf) wrote :

Verificaiton: I ran the [Test Case] on each of bionic, cosmic & disco w/o experiencing a hang or connection reset.

tags: added: verification-done verification-done-bionic verification-done-cosmic verification-done-disco
removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iperf - 2.0.12+dfsg1-2ubuntu0.1

---------------
iperf (2.0.12+dfsg1-2ubuntu0.1) disco; urgency=medium

  * Add backlog_increase.patch to fix hangs and connection resets
    with high thread count. LP: #1832399.
  * Add signal_bug.patch to fix issue with the server not exiting
    via SIGINT. LP: #1832401.

 -- dann frazier <email address hidden> Mon, 17 Jun 2019 12:40:32 -0600

Changed in iperf (Ubuntu Disco):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for iperf has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iperf - 2.0.10+dfsg1-1ubuntu1.1

---------------
iperf (2.0.10+dfsg1-1ubuntu1.1) cosmic; urgency=medium

  * Add backlog_increase.patch to fix hangs and connection resets
    with high thread count. LP: #1832399.
  * Add signal_bug.patch to fix issue with the server not exiting
    via SIGINT. LP: #1832401.

 -- dann frazier <email address hidden> Mon, 17 Jun 2019 13:08:17 -0600

Changed in iperf (Ubuntu Cosmic):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iperf - 2.0.10+dfsg1-1ubuntu0.18.04.2

---------------
iperf (2.0.10+dfsg1-1ubuntu0.18.04.2) bionic; urgency=medium

  * Add backlog_increase.patch to fix hangs and connection resets
    with high thread count. LP: #1832399.
  * Add signal_bug.patch to fix issue with the server not exiting
    via SIGINT. LP: #1832401.

 -- dann frazier <email address hidden> Mon, 17 Jun 2019 13:16:49 -0600

Changed in iperf (Ubuntu Bionic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.