-
Notifications
You must be signed in to change notification settings - Fork 267
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
Please document which kernel options are needed for procmon to work #74
Comments
@krzyk could you share the details of your environment? OS? Kernel? Are you attempting to run Procmon inside WSL? |
If you enable all options for bcc, then you should be able to use this without issue. BCC project makes it quick and easy to determine the kernel options needed. https://github.com/iovisor/bcc/blob/master/INSTALL.md#kernel-configuration |
@krzyk could you share the details of your environment? OS? Kernel? Are you attempting to run Procmon inside WSL? |
I'm getting the same error bpf: Failed to load program: Invalid argument debian 11 bullseye with these libraries |
Hey - looks like it failed verification. We're aware of verifier errors on some distros/versions and will look into it as soon as we can. |
I was looking for that exact error or something close and ran across this https://opendev.org/starlingx/kernel/commit/15a50452ba9b483b4949437e960dea4932a7b26c Several of the kernel config flags for bpf are disabled in my kernel config. Would enabling them fix the issue we are seeing. |
I just installed procmon (from the source) and when I do
sudo procmon
I get:So it looks like this needs some kernel options to use, it would be good to document that in README.md
EDIT: After enabling the needed kernel option and running procmon as root I get empty list (just the header and footer) and in the shell I see following errors:
So something is still missing, but what? (I have BPF enabled in kernel, but not sure if all the required options, or maybe I need some CLI tools?)
The text was updated successfully, but these errors were encountered: