Open louisroyer opened 3 years ago
Sorry for late reply. I don't see a mistake right away, but this could be cause by the currently out-dated quicly version that qperf uses. I will update this in the near future.
Just updated to newest quicly version. Could you please try if this issue is still preset with updated qperf? Make sure to run git submodule update --recursive
after you pull the newest commit.
After updating qperf and rebuilding my docker images, I still have this issue:
qperf-client | [2022-02-27T11:56:41+00:00] Running client-entrypoint.sh
qperf-client | [2022-02-27T11:56:41+00:00] Starting client in 5 seconds.
qperf-server | [2022-02-27T11:56:41+00:00] Running server-entrypoint.sh
qperf-server | [2022-02-27T11:56:41+00:00] Change working directory to /qperf
qperf-client | qperf: /qperf/extern/quicly/lib/quicly.c:494: lock_now: Assertion `is_reentrant && "caller must be reentrant"' failed.
qperf-client | /usr/local/bin/entrypoint.sh: line 12: 11 Aborted (core dumped) qperf "$@"
qperf-client | [2022-02-27T11:56:46+00:00] Running client-exitpoint.sh
qperf-client exited with code 0
qperf-server | starting server with pid 11, port 18080, cc reno, iw 10
qperf-server | got new connection
qperf-server | request received, sending data
qperf-server | connection 0 second 0 send window: 16890 packets sent: 27 packets lost: 0
qperf-server | connection 0 second 1 send window: 16890 packets sent: 2 packets lost: 0
qperf-server | connection 0 second 2 send window: 16890 packets sent: 0 packets lost: 0
^CGracefully stopping... (press Ctrl+C again to force)
Also, git submodule update --recursive
is well run.
Hello, when running a qperf server and a qperf client, on client side I have the following error then client exits:
Have I done any mistake?
Here is my setup (using docker-compose): https://github.com/louisroyer/qperf-docker/tree/v1.0.0
Full logs here:
Regards