Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

Avoid "unmatched close events" #19

Open
schu opened this issue Feb 16, 2017 · 0 comments
Open

Avoid "unmatched close events" #19

schu opened this issue Feb 16, 2017 · 0 comments

Comments

@schu
Copy link
Contributor

schu commented Feb 16, 2017

We only expect to see "unmatched close events" for connections initiated before tcptracer-bpf was started. Currently, we also see them for any TCP connection where tcp_*_connect didn't succeed (for example when connecting to a closed port) as we don't report those events:

https://github.com/weaveworks/tcptracer-bpf/blob/master/tcptracer-bpf.c#L415-L419

To reproduce, run the test tracer (sudo -E ./tests/tracer) and connect to a closed port, e.g. nc -w 1 google.com 56789

xref weaveworks/scope#2135 (comment)

sunhay added a commit to DataDog/tcptracer-bpf that referenced this issue Feb 21, 2019
Adding TCP tracing tests (and benchmarks)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant