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

Misleading libbpf FAILED logs #613

Closed
UltraInstinct14 opened this issue Apr 1, 2024 Discussed in #612 · 0 comments
Closed

Misleading libbpf FAILED logs #613

UltraInstinct14 opened this issue Apr 1, 2024 Discussed in #612 · 0 comments

Comments

@UltraInstinct14
Copy link
Contributor

Discussed in #612

Originally posted by jamroks April 1, 2024

Hi,
i launch an x86_64 ubuntu instance on a public subnet inside an aws vpc. i used this command :

docker run -u root --cap-add SYS_ADMIN --net=host --restart unless-stopped --privileged -dit -v /dev/log:/dev/log --name loxilb ghcr.io/loxilb-io/loxilb:latest --host=0.0.0.0

name -r

6.5.0-1016-aws

i tail the logs to take a look at the bootstrap and i found this error , i don't really know what it is , but i was concern since it's about ebpf

libbpf: failed to statfs /opt/loxilb/dp/bpf: No such file or directory

You can found an extract of the logs attached to this issue
loxilb.txt

please can you help me understand this error and how to troubleshoot

UltraInstinct14 added a commit that referenced this issue Apr 1, 2024
gh-613 Fixed certain misleading logs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants