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.

Sign up for GitHub

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

Jump to bottom

iperf3 segfault ld-musl-x86_64.so on Alpine Linux container #1692

Open
ryjogo opened this issue May 1, 2024 · 1 comment
Open

iperf3 segfault ld-musl-x86_64.so on Alpine Linux container #1692

ryjogo opened this issue May 1, 2024 · 1 comment

Comments

@ryjogo
Copy link

ryjogo commented May 1, 2024

Context

  • Version of iperf3:
/ # /usr/bin/iperf3 -v
iperf 3.16 (cJSON 1.7.15)
Linux store-speedtest-store-speedtest-client-9f5778c6f-t89q9 6.1.80-talos #1 SMP Wed Mar  6 12:03:30 UTC 2024 x86_64
Optional features available: CPU affinity setting, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication, bind to device, support IPv4 don't fragment, POSIX threads

  • Hardware:
    8GB RAM, 6 Cores VM on a Proxmox Node

  • Operating system (and distribution, if any):

iperf3 is running within a container on Kubernetes, using Talos Linux, the container is of Alpine LInux.

Kernel:

/ # uname -a
Linux store-speedtest-store-speedtest-client-9f5778c6f-t89q9 6.1.80-talos #1 SMP Wed Mar  6 12:03:30 UTC 2024 x86_64 Linux

Distribution:

/ # cat /etc/alpine-release
3.19.1
  • Other relevant information (for example, non-default compilers,
    libraries, cross-compiling, etc.):

Bug Report

  • Expected Behavior

  • Actual Behavior
    Logs:

kern:    info: [2024-04-30T16:22:47.33176344Z]: iperf3[16828]: segfault at 7fdefe920b74 ip 00007fdefee065bb sp 00007ffdba47f6a0 error 6 in ld-musl-x86_64.so.1[7fdefedbf000+54000] likely on CPU 3 (core 1, socket 1)
kern:    info: [2024-04-30T16:22:47.33346444Z]: Code: c6 40 40 01 c3 50 48 83 cf ff e8 05 0a 00 00 55 53 48 89 fb 48 81 ec a8 00 00 00 8b 05 3e 6a 04 00 85 c0 74 2d b8 01 00 00 00 <89> 43 3c f0 83 0c 24 00 e8 a8 23 00 00 48 39 c3 74 70 48 81 c4 a8
kern:    info: [2024-04-30T17:23:00.29008344Z]: iperf3[18058]: segfault at 7f1814235b74 ip 00007f181471b5bb sp 00007fff79cab440 error 6 in ld-musl-x86_64.so.1[7f18146d4000+54000] likely on CPU 0 (core 0, socket 0)
kern:    info: [2024-04-30T17:23:00.29139644Z]: Code: c6 40 40 01 c3 50 48 83 cf ff e8 05 0a 00 00 55 53 48 89 fb 48 81 ec a8 00 00 00 8b 05 3e 6a 04 00 85 c0 74 2d b8 01 00 00 00 <89> 43 3c f0 83 0c 24 00 e8 a8 23 00 00 48 39 c3 74 70 48 81 c4 a8
kern:    info: [2024-04-30T19:23:13.28862044Z]: iperf3[20481]: segfault at 7f0d68bc7b74 ip 00007f0d690ad5bb sp 00007ffe23056240 error 6 in ld-musl-x86_64.so.1[7f0d69066000+54000] likely on CPU 1 (core 1, socket 0)
kern:    info: [2024-04-30T19:23:13.29005844Z]: Code: c6 40 40 01 c3 50 48 83 cf ff e8 05 0a 00 00 55 53 48 89 fb 48 81 ec a8 00 00 00 8b 05 3e 6a 04 00 85 c0 74 2d b8 01 00 00 00 <89> 43 3c f0 83 0c 24 00 e8 a8 23 00 00 48 39 c3 74 70 48 81 c4 a8
kern:    info: [2024-04-30T19:23:51.11926844Z]: iperf3[20623]: segfault at 7f3ff328fb74 ip 00007f3ff37755bb sp 00007ffe0a917cd0 error 6 in ld-musl-x86_64.so.1[7f3ff372e000+54000] likely on CPU 3 (core 1, socket 1)
kern:    info: [2024-04-30T19:23:51.12061444Z]: Code: c6 40 40 01 c3 50 48 83 cf ff e8 05 0a 00 00 55 53 48 89 fb 48 81 ec a8 00 00 00 8b 05 3e 6a 04 00 85 c0 74 2d b8 01 00 00 00 <89> 43 3c f0 83 0c 24 00 e8 a8 23 00 00 48 39 c3 74 70 48 81 c4 a8
kern:    info: [2024-04-30T19:24:33.06359544Z]: iperf3[20712]: segfault at 7f5a8ec86b74 ip 00007f5a8f16c5bb sp 00007ffcafa21380 error 6 in ld-musl-x86_64.so.1[7f5a8f125000+54000] likely on CPU 3 (core 1, socket 1)
kern:    info: [2024-04-30T19:24:33.06460444Z]: Code: c6 40 40 01 c3 50 48 83 cf ff e8 05 0a 00 00 55 53 48 89 fb 48 81 ec a8 00 00 00 8b 05 3e 6a 04 00 85 c0 74 2d b8 01 00 00 00 <89> 43 3c f0 83 0c 24 00 e8 a8 23 00 00 48 39 c3 74 70 48 81 c4 a8
  • Steps to Reproduce
    Command:
    /usr/bin/iperf3 -c <host> --json -P 2 -t 10
@ryjogo ryjogo changed the title iperf3 segfault ld-musl-x86_64.so iperf3 segfault ld-musl-x86_64.so on Alpine LInux Container May 1, 2024
@ryjogo ryjogo changed the title iperf3 segfault ld-musl-x86_64.so on Alpine LInux Container iperf3 segfault ld-musl-x86_64.so on Alpine LInux container May 1, 2024
@ryjogo ryjogo changed the title iperf3 segfault ld-musl-x86_64.so on Alpine LInux container iperf3 segfault ld-musl-x86_64.so on Alpine Linux container May 1, 2024
@davidBar-On
Copy link
Contributor

I built and run iperf3 under Alpine container, when Docker is running under Windows 11 / WSL2 (Ubuntu Linux). The command run o.k. The Dockerfile I used to build the container is:

FROM alpine:latest
RUN apk update && apk upgrade && apk add openssl ca-certificates
RUN apk --no-cache --virtual build-dep add g++ gcc openssl-dev make git automake autoconf

RUN git clone https://github.com/esnet/iperf.git --branch master

RUN cd iperf && ./configure && \
    make install && \
    apk del build-dep automake autoconf && \
    rm -rf /iperf3

The container build command: docker build -t alpine-sh Dockerfile.

The system/iperf3 info:

docker run --rm -ti alpine-sh cat /etc/alpine-release
3.19.1

docker run --rm -ti alpine-sh uname -a
Linux 5f7c8ecfcbda 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 Linux

docker run --rm -ti alpine-sh /usr/local/bin/iperf3 -v
iperf 3.16+ (cJSON 1.7.15)
Linux 509f1cff6ea4 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64
Optional features available: CPU affinity setting, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication, bind to device, support IPv4 don't fragment, POSIX threads

Did you use similar steps to build and run iperf3 in the container? If not, how did you build iperf3? If yes, the problem may be related to platform you are using or the Talos Linux. Is there a way that you can run iperf3 under GDB (or other debugger), so it will be possible to identify were the fault happens? (If a core dump is generated, then it may also be analyzed.)

@vincejv vincejv mentioned this issue Jul 28, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ryjogo @davidBar-On