search

esnet / iperf

iperf3: A TCP, UDP, and SCTP network bandwidth measurement tool
Other
6.81k stars 1.27k forks source link

Problem with iperf3 running in background for more than 5 min #924

Open smgagan opened 4 years ago

smgagan commented 4 years ago

Hi team, I have a similar issue mentioned in this link [(https://github.com/esnet/iperf/issues/661)]

Version of iperf3: 3.7 (Cjson 1-5-2)

Operating System: Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS OS type 64 bit

I am running iperf3 on two separate laptops. And saving the output in json files.

Please guide me.

Best Regards, Gagan.

bmah888 commented 4 years ago

Need some more details. What are the command lines you're using on the client and server? Are they running in special environments (such as a screen session), or are you just running them in background from the shell?

What happens on the client and server?

If you can test without using JSON output, then you can see the output in more-or-less real time, so that might give you some insight into what's happening. Having that output might be useful to others attempting to help you, also.

smgagan commented 4 years ago

Hi, please find the command lines as mentioned below. Client Side: iperf3 -c -ip adress -p 5201 -i 1 -b 500M -t 1800 -u -J --logfile /home/---/filename.json Server Side: iperf3 -s

Environment: Our company is in the R&D of cellular communication where complete LTE network is set up. Iperf3 Client and Server are running on separate laptop. Both the laptops are connected to USB3 dongle type device in which SIM cards can be inserted. These SIM cards will be connected to our network. The above commands are generated from JupyterNotebook. However I tried without JNotebook also, the output remains same.

I have ran the test without using JSON output and the behavior is same. Almost after 5 to 8 minutes, the server side will show 'Bad file descriptor' or just stops receiving (0 bytes).

I haven't taken screenshots but I will post it next time.

bmah888 commented 4 years ago

This doesn't really sound like an iperf3 issue.

Just to confirm are you actually seeing output on the client side during those first 5 minutes? Also what happens if you run iperf3 in the foreground as opposed to background? Have you considered using the nohup command available in many shells (under certain circumstances, shell auto-logout could cause this kind of a problem)?