-
Notifications
You must be signed in to change notification settings - Fork 164
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
Seemingly inconsistent behavior when using "args" argument in different namespaces #109
Comments
I took a look at this again and these lines in the
Looking at the URL in question, there is no entry for the Running this script locally (MacOS with the supplied version of AWK; i.e., BSD AWK and not GNU AWK), I get |
This is my first day using
kubectl-trace
, so I apologize if this is a silly question/if my assessment of it is wrong.output of
kubectl trace version
:git commit: d34d1d5
build date: 2019-09-19 09:00:13 -0600 MDT
output of
uname -r
on the node:5.4.0-1009-aws
(Ubuntu 20.04 AMI)Platform:
AWS (with kops)
Problem:
I've been able to successfully run this command:
kubectl trace run -e "tracepoint:syscalls:sys_enter_* { if(args->ret < 0) {@[ustack] = count();} }" pod/some-pod -a
However, when I try to run this command in a different namespace (on a pod in the
kube-system
namespace for example), I get:Steps taken:
At first I thought it had something to do with trying to use the default service account, but following the instructions in the readme does not appear to make a difference.
Afterwards, I noticed this issue on bpftrace which seems to indicate that this is an issue with headers not being installed; however, running the same command with
--fetch-headers
appended yields:When changing the bpftrace expression to just:
"tracepoint:syscalls:sys_enter_* { @[ustack] = count(); }
, then it works regardless of pod/namespace, which leads me to believe that it has something to do with theargs
parameter.Apologies again if this the wrong place to ask this kind of question or if my assessment of my problem is incorrect.
The text was updated successfully, but these errors were encountered: