iperf3: error - unable to read from stream socket: Bad file descriptor

[gangadharamL]

Hi ,

I am facing the below issue while running the iperf3 with sctp , but it's terminating with below errors

server side:
iperf3 -s

Server listening on 5201

Accepted connection from 192.x.x.x, port 43122
[ 5] local 192.x.x.x port 5201 connected to 192.x.x.x port 63208
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 119 KBytes 974 Kbits/sec
[ 5] 1.00-2.00 sec 122 KBytes 1.00 Mbits/sec
[ 5] 2.00-3.00 sec 120 KBytes 985 Kbits/sec
iperf3: error - unable to read from stream socket: Bad file descriptor

client side :
iperf3 -c 192.x.x.x --sctp -p 5201 -b 1M -t 30 -l 1
Connecting to host 192.x.x.x, port 5201
[ 4] local 192.x.x.x port 63208 connected to 192.x.x.x port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 121 KBytes 989 Kbits/sec
[ 4] 1.00-2.00 sec 121 KBytes 994 Kbits/sec
[ 4] 2.00-3.00 sec 122 KBytes 996 Kbits/sec
iperf3: error - control socket has closed unexpectedly

I am using the below iperf3 version

iperf3 -v
iperf 3.1.3
Linux vm 5.16.4-1.el7.elrepo.x86_64 #1 SMP PREEMPT Fri Jan 28 08:23:05 EST 2022 x86_64
Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing

can some one suggest on the above issue

[davidBar-On]

iperf 3.1.3 is a very very old version. Although I am not sure whether that that will help, suggest to upgrade to a newer version and retry the test.

Usually such issues are caused because of a problem in the connection between the server and the client. Can you give move details, e.g., does this problem happen all the time? When it happens, is it always after about 4 seconds? E.tc.