Skip to content
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

No profiles found in ClickHouse based on eBPF #224

Closed
syzhang42 opened this issue May 14, 2024 · 3 comments
Closed

No profiles found in ClickHouse based on eBPF #224

syzhang42 opened this issue May 14, 2024 · 3 comments

Comments

@syzhang42
Copy link

The interface shows that there is no eBPF data in clickhouse, but I installed it at helm and there are agents in the cluster. What is the reason for this?
My coroot interface:
image
My cluster's pods:
image
Is it because you need to do some additional Settings?
My kernel version:
5.15.0-52-generic

@grzesuav
Copy link

Installed coroot today and have similar case, I do not see errors in node-agent logs, is there anything particular I should look at ?

@grzesuav
Copy link

In my case it seems it cannot find

I0517 12:52:26.266655   14417 profiling.go:52] profiles endpoint: http://coroot:8080/v1/profiles
E0517 12:52:26.361455   14417 profiling.go:100] link kprobes: link kprobe disassociate_ctty: creating tracefs event (arch-specific fallback for "disassociate_ctty"): creating probe entry on tracefs: open /sys/kernel/tracing/kprobe_events: no such file or directory
E0517 12:52:26.361455   14417 profiling.go:100] link kprobes: link kprobe disassociate_ctty: creating tracefs event (arch-specific fallback for "disassociate_ctty"): creating probe entry on tracefs: open /sys/kernel/tracing/kprobe_events: no such file or directory
E0517 12:52:26.361455   14417 profiling.go:100] link kprobes: link kprobe disassociate_ctty: creating tracefs event (arch-specific fallback for "disassociate_ctty"): creating probe entry on tracefs: open /sys/kernel/tracing/kprobe_events: no such file or directory
E0517 12:52:26.361455   14417 profiling.go:100] link kprobes: link kprobe disassociate_ctty: creating tracefs event (arch-specific fallback for "disassociate_ctty"): creating probe entry on tracefs: open /sys/kernel/tracing/kprobe_events: no such file or directory

while on host

$ pwd && ls -al
/sys/kernel/tracing
total 0
drwx------   6 root root 0 Jan  1  1970 .
drwxr-xr-x  13 root root 0 May 17 12:10 ..
-r--r--r--   1 root root 0 Jan  1  1970 README
-r--r--r--   1 root root 0 Jan  1  1970 available_events
-r--r--r--   1 root root 0 Jan  1  1970 available_tracers
-r--r--r--   1 root root 0 Jan  1  1970 buffer_percent
-rw-r--r--   1 root root 0 Jan  1  1970 buffer_size_kb
-r--r--r--   1 root root 0 Jan  1  1970 buffer_total_size_kb
-rw-r--r--   1 root root 0 Jan  1  1970 current_tracer
-rw-r--r--   1 root root 0 Jan  1  1970 dynamic_events
-rw-r--r--   1 root root 0 Jan  1  1970 error_log
drwxr-x--- 102 root root 0 Jan  1  1970 events
--w-------   1 root root 0 Jan  1  1970 free_buffer
drwxr-x---   2 root root 0 Jan  1  1970 instances
drwxr-x---   2 root root 0 Jan  1  1970 options
drwxr-x---  10 root root 0 Jan  1  1970 per_cpu
-r--r--r--   1 root root 0 Jan  1  1970 printk_formats
-r--r--r--   1 root root 0 Jan  1  1970 saved_cmdlines
-rw-r--r--   1 root root 0 Jan  1  1970 saved_cmdlines_size
-r--r--r--   1 root root 0 Jan  1  1970 saved_tgids
-rw-r--r--   1 root root 0 Jan  1  1970 set_event
-rw-r--r--   1 root root 0 Jan  1  1970 set_event_notrace_pid
-rw-r--r--   1 root root 0 Jan  1  1970 set_event_pid
-r--r--r--   1 root root 0 Jan  1  1970 timestamp_mode
-rw-r--r--   1 root root 0 Jan  1  1970 trace
-rw-r--r--   1 root root 0 Jan  1  1970 trace_clock
--w--w----   1 root root 0 Jan  1  1970 trace_marker
--w--w----   1 root root 0 Jan  1  1970 trace_marker_raw
-rw-r--r--   1 root root 0 Jan  1  1970 trace_options
-r--r--r--   1 root root 0 Jan  1  1970 trace_pipe
-rw-r--r--   1 root root 0 Jan  1  1970 tracing_cpumask
-rw-r--r--   1 root root 0 Jan  1  1970 tracing_on
-rw-r--r--   1 root root 0 Jan  1  1970 tracing_thresh
-rw-r--r--   1 root root 0 Jan  1  1970 uprobe_events
-r--r--r--   1 root root 0 Jan  1  1970 uprobe_profile

@syzhang42
Copy link
Author

hi,My profile can be collected but cannot be uploaded. The agent log information is as follows.
profiling.go:152] Post "%E2%80%9C%E2%80%9D?container.id=%2Fk8s%2Fcoroot%2Fcoroot-cluster-agent-6556cfbf54-md52x%2Fcluster-agent&host.id=6e2adec807da490bbdfe58cba285412d&host.name=ebpf-node1&service.name=%2Fk8s%2Fcoroot%2Fcoroot-cluster-agent": unsupported protocol scheme ""
Why is my profile endpoint a garbled text?
I0520 03:03:22.770895 918384 profiling.go:52] profiles endpoint: %E2%80%9C%E2%80%9D
My values.yaml is as follows:
node-agent: enabled: true tracesEndpoint: "http://coroot:8080/v1/traces" logsEndpoint: "http://coroot:8080/v1/logs" profilesEndpoint: "http://coroot:8080/v1/profiles"
Please help me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants