-
Notifications
You must be signed in to change notification settings - Fork 68
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
Fail to start up with: Failed to probe tracepoint #2976
Comments
Hi @jpmeijers , Can you please check if your kernel was compiled with CONFIG_HAVE_SYSCALL_TRACEPOINTS=y ? |
Same question for CONFIG_FTRACE_SYSCALLS |
Possibly, this is fixed by #2990 |
Presumably related: evilsocket/opensnitch#774 |
@jpmeijers , can you please try again with the most recent image? |
I tried the new container version on two different hosts. A physical Dell server running Unraid, and a VM running Ubuntu 20.04. Both fail with the same error:
Unraid:
VM + Ubuntu:
|
The tracepoint error has however been replaced by a warning, so this issue can be closed. I'll have to open a new one about eBPF.
|
Can you say more about how this VM was installed/built and how you're running parca-agent? In particular are you running it as root? (It needs to be run as root.) I just installed a fresh copy of Ubuntu 20.04 Desktop on a VirtualBox VM and can't repro, so there must be some weird difference between our setups. |
Running parca-agent in Docker on Unraid 7.0.0-beta.2.
The container exits soon after startup due to it not finding
/sys/kernel/debug/tracing/events/syscalls/sys_enter_mmap/id
.Looking at the host, the kernel debugfs is mounted, but the syscalls directory does not exist.
The text was updated successfully, but these errors were encountered: