-
Notifications
You must be signed in to change notification settings - Fork 897
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
Uninstall/update should rmmod (old) kernel module #418
Comments
from a
|
/var/log/messages
|
The same has occurred on another similar system:
|
System info:
|
Issue has occurred on a debian machine also, so doesn't appear to be OS-dependent:
|
majorsimon
changed the title
Uninstall should rmmod kernel module
Uninstall/update should rmmod (old) kernel module
Sep 17, 2018
mstemm
added a commit
that referenced
this issue
Nov 6, 2018
When falco is started, load the kernel module. (The falco binary also will do a modprobe if it can't open the inspector, as a backup). When falco is stopped, unload the kernel module. This fixes #418.
This was referenced Nov 6, 2018
mstemm
added a commit
that referenced
this issue
Nov 6, 2018
* Load/unload kernel module on start/stop When falco is started, load the kernel module. (The falco binary also will do a modprobe if it can't open the inspector, as a backup). When falco is stopped, unload the kernel module. This fixes #418. * Put script execute line in right place.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During a recent update from v0.11.1 to v.0.12.1, we were hit with segmentation fault issues. After investigation, it appears that the old kernel module had not been unloaded. An execution of
rmmod falco_probe && modprobe falco_probe && systemctl restart falco
resolved the issue.The text was updated successfully, but these errors were encountered: