Skip to content
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

Verbose mode used with Parallel streams causes iperf3 to stop #686

Closed
ExpandingScope opened this issue Jan 12, 2018 · 1 comment
Closed
Assignees
Labels
Milestone

Comments

@ExpandingScope
Copy link

Context

Bug Report

  • Actual Behavior
    When using Verbose mode on the server and Parallel streams on the client. The iperf on the server will stop and the client will not display all results.

  • Steps to Reproduce
    A server in verbose mode "iperf3 -s -V" and running the client with multiple threads "iperf3 -P2 -c x.x.x.x".
    The client reports "iperf3: error - control socket has closed unexpectedly" and stops before displaying the last second and summary results. The server end will show results but will stop functioning and have to be restarted due to "Segmentation fault (core dumped)"

Server: iperf3 -s -V
Client: iperf3 -P2 -c x.x.x.x

  • Possible Solution
    Unknown
@bmah888 bmah888 self-assigned this Jan 12, 2018
@bmah888 bmah888 added the bug label Jan 12, 2018
@bmah888
Copy link
Contributor

bmah888 commented Jan 12, 2018

First, thanks for a well-researched and well-written bug report. I'm able to reproduce the problem you reported on iperf-3.3 and master (single CentOS 7 host acting as both client and server). No idea what the problem is at this point but appears to be a Real Bug (tm).

bmah888 added a commit that referenced this issue Jan 26, 2018
…nections.

This was caused by a stale / invalid pointer reference that didn't even
make any sense in context anyway.  Fixes #686.
@bmah888 bmah888 added this to the 3.4 milestone Jan 26, 2018
bmah888 added a commit that referenced this issue Jan 26, 2018
…nections. (#696)

This was caused by a stale / invalid pointer reference that didn't even
make any sense in context anyway.  Fixes #686.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants