-
Notifications
You must be signed in to change notification settings - Fork 1
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
error compiling module for program "cachestat" #3
Comments
Thanks for pointing this out! ebpf_exporter needs libbcc/bcc. Here is a similar issue with more information: Sysinternals/ProcMon-for-Linux#13 To make this work again, we need to update the Dockerfile for the ebpf_exporter and most likely have to compile libbcc/bcc ourselves as the debian package has not been updated. The bug is in https://github.com/rcrane/TEEMon/blob/master/exporters/ebpf_exporter/Dockerfile at lines 10-12. For clarification, could you state the kernel version of your host machine? |
Thanks for your prompt following-up. I am currently using |
Integrating https://github.com/iovisor/bcc/releases/tag/v0.18.0 into the Dockerfile (compilation part) of the ebpf_exporter might solve the issue. |
According to our discussion, does it suffice to modify both Line 12 and Line 31 in the
with
? |
I crafted a wip fix: https://github.com/rcrane/TEEMon/tree/update-ebpf_exporter |
Thanks for your comprehensive help! The previous error seems to be mitigated, however, the container
I just ran with the latest |
Your latest issue sounds like it is something different. |
Alright. I will open another issue and try to give a base for you to reproduce the issue. Thanks again for your support! |
Hi TEEMon Team,
When I followed the instructions in
README.md
, I finally made to start the six containers (i.e., prometheus, grafana, sgx-exporter, node-exporter, ebpf-exporter, cadvisor) after fixing Issue #1 with #2. However, the next challenge I faced was that theebpf_exporter
kept restarting, as shown in the sample result of executingdocker ps
:I then tried to take a look at
ebpf_exporter
's log. It contained something likeIt seems to be an ``inherenet'' problem, which has nothing to do with my operations.
I am wondering if your team has met this issue before? If yes, could you possibly tell me what I should do to mitigate the issue? Thanks a lot!
The text was updated successfully, but these errors were encountered: