search

coroot / coroot-node-agent

A Prometheus exporter based on eBPF that gathers comprehensive container metrics
https://coroot.com/docs/metrics/node-agent
Apache License 2.0
318 stars 59 forks source link

RX timestamp: no timestamp found #90

Open ttkkxfkl opened 4 months ago

ttkkxfkl commented 4 months ago

E0528 22:45:11.952218 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952133 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952133 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952133 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952133 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952278 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952278 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952278 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952278 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952302 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952302 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952302 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found E0528 22:45:11.952302 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found W0528 22:45:11.953642 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.953642 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.967648 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.967648 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.968086 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.968086 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.973091 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.973091 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.980331 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address W0528 22:45:11.980331 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address

Are the above logs normal? I haven't found the reason why these logs are printed. Is it related to the listening docker container or the kernel?

ttkkxfkl commented 4 months ago

E0528 22:45:11.952302 2630039 pinger.go:94] failed to get RX timestamp: no timestamp found W0528 22:45:11.953642 2630039 container.go:851] failed to send packet to ::1: write ip4 0.0.0.0->::1: address ::1: non-IPv4 address