esnet
"unable to create a new stream: No such file or directory" when running iperf3 -c on Intel TDX platform
NOTE: The iperf3 issue tracker is for registering bugs, enhancement requests, or submissions of code. It is not a means for asking questions about building or using iperf3. Those are best directed towards the Discussions section for this project at https://github.com/esnet/iperf/discussions or to the iperf3 mailing list at [email protected]. A list of frequently-asked questions regarding iperf3 can be found at http://software.es.net/iperf/faq.html.
Context
-
Version of iperf3: latest code base.
-
Hardware: intel TEE(trust execution environment) platform: TDX
-
Operating system (and distribution, if any): ubuntu22.04
Please note: iperf3 is supported on Linux, FreeBSD, and macOS. Support may be provided on a best-effort basis to other UNIX-like platforms. We cannot provide support for building and/or running iperf3 on Windows, iOS, or Android.
- Other relevant information (for example, non-default compilers, libraries, cross-compiling, etc.):
Please fill out one of the "Bug Report" or "Enhancement Request" sections, as appropriate. Note that submissions of bug fixes, new features, etc. should be done as a pull request at https://github.com/esnet/iperf/pulls
Bug Report
Connecting to host xxx.xxx.xxx.xxx, port 5001 iperf3: error - unable to create a new stream: No such file or directory
-
Expected Behavior iperf3 client side get iperf result correctly.
-
Actual Behavior Connecting to host xxx.xxx.xxx.xxx, port 5001 iperf3: error - unable to create a new stream: No such file or directory
-
Steps to Reproduce
-
iperf3 -s -p 5001 (this runs correctly)
-
iperf3 -c xxx.xxx.xxx.xxx -p 5001 (unable to create a new stream)
-
Possible Solution unlink(template) after ftruncate would solve this issue.
We're having trouble reproducing this issue. Were you using the same computer for client and server? Is the problem intermittent? Does it still happen with the latest code base?
Closing for now due to lack of response, but feel free to reopen it in the future, if it's still an issue.