-
Notifications
You must be signed in to change notification settings - Fork 352
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
Problems running gRPC server, misteriously led to failure attaching event_exit_acct_process
on latest version
#2263
Comments
Thanks @inliquid, Is Oracle Linux using lockdown by any chance? What's the output of:
|
Yes it seems so:
|
This mode prohibits loading BPF programs, which means that Tetragon cannot really work. We suggest to switch to "integrity" instead. See iovisor/bcc#2565 for more discussion on this. There is a PR from @tixxdz to issue an early warning about this: #2149. |
Given that we now have an issue to add the documentation for lockdown-related issues: I'll close this issue, feel free to reopen this if you still have issues with this and this will not be addressed by #2265 being resolved. |
What happened?
This issue stated as a discussion with several participants who had mostly the same problem with Tetragon v1.0.0-v1.0.2.
Symptoms are:
tetra
being connected to Tetragon over gRPCWhen this line is present there should be goroutine started with gRPC server instance.
However, what we observed is that for some mysterious reason it's not run, and stack trace shows no such goroutine - try search for "grpc" in the stack trace output:
Here is
gops 1
output in our case, it's clear that gRPC server is not run:After upgrade to latest CI image with help of these command:
Tetragon start failing to start with this message:
OS is Oracle Linux 8.5 with CONFIG_BSD_PROCESS_ACCT enabled
Also:
Tetragon Version
v1.0.0, v1.0.2, latest CI
Kernel Version
5.4.17-2136.304.4.1.el8uek.x86_64
Kubernetes Version
No response
Bugtool
No response
Relevant log output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: