Menu

iperf 2.0.12 "write failed" issue

JUN.XIAO
2018-12-11
2018-12-12
  • JUN.XIAO

    JUN.XIAO - 2018-12-11

    Hi,Sirs:
    I uesed iperf version 2.0.12 in CentOS7.5, and found that:
    When I try a multi-thread test for iperf server, some "wirte failed" error will print. Then the server cannot count the failed thread even if it reset and connect successful.
    I tested it like this:
    1. enable iperf server in 192.168.1.15: "iperf -s -p 5002"
    2. try connecting in 192.168.1.16: "iperf -c 192.168.1.15 -p 5002 -t 30 -i 3 -P 64"
    after step2, some error logs like this :"write failed: Connection reset by peer" will print out,

    I can find that: 
    1. Though in client end all 64 threads run well, the server end only show part of them.
    2. The number of connetion printed by server add the number of "write failed" connection printed by client is just equal 64, which means the reset threads is not counted by server.
    3. "write failed" only happened when threads too much, such as -P 64. If you use the option -P 10, everything is OK.
    

    ** I think this maybe a bug for server-end? Is anybody want to rectify this issue?**

     
    • Robert McMahon

      Robert McMahon - 2018-12-12

      Can you verify the file limits?

      https://www.tecmint.com/increase-set-open-file-limits-in-linux/

      Also, possibly try the latest 2.0.13a from sourceforge

      https://sourceforge.net/projects/iperf2/

      Thanks,
      Bob

      Hi,Sirs:
      I uesed iperf version 2.0.12 in CentOS7.5, and found that:
      When I try a multi-thread test for iperf server, some "wirte failed"
      error will print. Then the server cannot count the failed thread even
      if it reset and connect successful.
      I tested it like this:
      1. enable iperf server in 192.168.1.15: "iperf -s -p 5002"
      2. try connecting in 192.168.1.16: "iperf -c 192.168.1.15 -p 5002 -t
      30 -i 3 -P 64"
      after step2, some error logs like this :"write failed: Connection
      reset by peer" will print out,

      I can find that:
      1. Though in client end all 64 threads run well, the server end only
      show part of them.
      2. The number of connetion printed by server add the number of "write
      failed" connection printed by client is just equal 64, which means the
      reset threads is not counted by server.
      3. "write failed" only happened when threads too much, such as -P 64.
      If you use the option -P 10, everything is OK.

      I THINK THIS MAYBE A BUG FOR SERVER-END? IS ANYBODY WANT TO RECTIFY
      THIS ISSUE?


      iperf 2.0.12 "write failed" issue [1]

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/iperf2/discussion/general/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

      *

      [1]
      https://sourceforge.net/p/iperf2/discussion/general/thread/cb147b7a1d/?limit=25#5411

       
      • JUN.XIAO

        JUN.XIAO - 2018-12-12

        Dear Bob:
        My platform is CentOS, and I cannot find 2.0.13a for linux.
        Also, I checked file limits, it looks as normal as what displayed on the web .

        At last,I tried iperf3, it looks work well, so can we use iperf3 instead of iperf2?
        What I want to confirm is that iperf3 can full compatible with iperf2 or not?
        
         

        Last edit: JUN.XIAO 2018-12-12
        • Robert McMahon

          Robert McMahon - 2018-12-12

          one has to compile iperf 2.0.13a from source. Use git to checkout the
          code then run

          ./configure
          ./make
          sudo ./make install

          Let me know if you try this and hit any issues.

          iperf3 does not interoperate with iperf2. It's a rewrite. There
          similar in many respects but different in others. Iperf 2 with -P uses
          threads and that's different from iperf 3 which is single threaded.

          Bob

          Dear Bob:
          My platform is CentOS, and I cannot find 2.0.13a for linux.
          I tried iperf3, it looks work well, so can we use iperf3 instead of
          iperf2?
          What I want to confirm is that iperf3 can full compatible with iperf2
          or not?


          iperf 2.0.12 "write failed" issue [1]

          Sent from sourceforge.net because you indicated interest in
          https://sourceforge.net/p/iperf2/discussion/general/

          To unsubscribe from further messages, please visit
          https://sourceforge.net/auth/subscriptions/

          *

          [1]
          https://sourceforge.net/p/iperf2/discussion/general/thread/cb147b7a1d/?limit=25#5411/57a8/0a59

           
          • JUN.XIAO

            JUN.XIAO - 2018-12-12

            Dear Bob:
            Thanks for your help. It looks iperf 2.0.13a work well, I cannot reproduce this issue with version 2.0.13a.
            If any issue tested, I will report again.

            BR.

             

Log in to post a comment.