Closed
Description
What happened?
<probe> WARN: 2020/05/07 16:30:46.704903 Error setting up the eBPF tracker, falling back to proc scanning: cannot write "p:ptcp_v4_connect tcp_v4_connect\n" to kprobe_events: write /sys/kernel/debug/tracing/kprobe_events: file exists
The symptom goes away on reboot, until you run a second time. It seems as though Scope is not clearing down the kprobes when it exits?
How to reproduce it?
scope launch
scope stop
scope launch
Versions:
This is on Ubuntu 20.04
$ uname -a
Linux vagrant 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux