-
Notifications
You must be signed in to change notification settings - Fork 728
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
Omit SIGKILL event in centos7 with kernel 3.10.0 #2000
Comments
Hi @liuyaqiu! I just tried but I cannot reproduce the issue with docker. Could you give a try with docker only? Has the host any particular configuration? Is the host on high load? |
Does this issue happen all the time? |
Difference to previous situation
Now the host machine load average is low: And I can see the SIGKILL events in time, sysdig works well. import os
import signal
import time
print("My PID is:", os.getpid())
# Sleep for 10 seconds
time.sleep(10)
# Kill self with SIGKILL
os.kill(os.getpid(), signal.SIGKILL) I run this script inside another container. The sysdig run also run inside a container while the
@therealbobo Now everything looks working well. Thanks for your help. And I will still pay attention to this problem to see whether it reproduces. |
The only thing I could think of (other than a bug in the drivers) is that |
I think sysdig may omit some event in centos7 with kernel 3.10.0
Runtime Information
System:
CentOS Linux release 7.9.2009 (Core)
Kernel:
3.10.0-1160.el7.x86_64
Sysdig:
0.35.1
Docker:
Problem
I want to detect SIGKILL signal event inside container.
So I run the below command on the host machine.
Below is the output.
kill inside container
Then I execute a
kill
command inside a k8s docker container located at this host machine.I cannot see the
kill
command's system call event in the first picture.kill inside host machine
Obviously, I still cannot see the
kill
command's event.Conclusion
I think
sysdig
cannot work well in the centos7 with kernel 3.10.0. Or how can I make it work well?The text was updated successfully, but these errors were encountered: