-
Notifications
You must be signed in to change notification settings - Fork 450
Unable to run Tracee locally #4635
-
I have a machine that running Ubuntu 24.04 LTS with custom Linux 6.12.1 kernel. I found that only docker are able to run Tracee but I have special requirement that must run Tracee locally. I use this command for docker and it works:
And I do these locally but fail with error message:
|
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 2 comments · 9 replies
-
@MrZLeo thanks for this report. Trying to reproduce it soon. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Not reproducible on 6.12.17.
It seems all right so far. @MrZLeo your log shows: P.S.: use ./dist/tracee (one-binary) instead of ./dist/tracee-{ebpf,rules} since the latter will be removed soon. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi @geyslan, thanks for you help! I built it in my host machine, no virtual environment (docker, vm...) involved. This is the whole logs I can give, and this procedure can be reproduced for me multiple times. I am wondering whether there are some difference between our kernel? libbpf reported permission denied because ebpf verification error:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Hello @MrZLeo, thanks for reporting this... we're happy to help you. Could you share the output of I've tried in my env and I was not able to reproduce the issue yet:
Please run
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi @rscampos , I am using upstream linux 6.12.1 kernel, which I compiled myself. I can reproduce this problem in archlinux as well, you can try to use newest archlinux virtual machine. I quickly looked the ebpf source code and found that Tracee use raw_tracepoint of execve syscall, which don't exist in original kernel as far as I know (only sys_enter and sys_exit raw tracepoint exist). Maybe this is a breaking change in trace subsystem of kernel? |
Beta Was this translation helpful? Give feedback.
All reactions
-
My full log:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
kernel version:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Thank you for the logs, @MrZLeo. @geyslan suggested that the issue might be related to the Clang version. Currently, we fully support Clang 14 (I'll update this in the future). I tested compiling Tracee and found that Clang 18 and 19 produce errors similar to yours. Are you using one of these versions? |
Beta Was this translation helpful? Give feedback.
All reactions
-
@rscampos Yes, that's it. I use Clang 19 in archlinux and Clang 18 in Ubuntu. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Nice... pls try with Clang 14 and share with us if you have any problem... soon we'll bump the clang version. |
Beta Was this translation helpful? Give feedback.
All reactions
-
yep,clang-14 is good.🥳 |
Beta Was this translation helpful? Give feedback.
All reactions
-
🚀 1
Thank you for the logs, @MrZLeo. @geyslan suggested that the issue might be related to the Clang version. Currently, we fully support Clang 14 (I'll update this in the future). I tested compiling Tracee and found that Clang 18 and 19 produce errors similar to yours. Are you using one of these versions?