coroot-node-agent icon indicating copy to clipboard operation
coroot-node-agent copied to clipboard

RX timestamp: no timestamp found

Open ttkkxfkl opened this issue 1 year ago • 3 comments

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 avatar May 29 '24 06:05 ttkkxfkl

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

ttkkxfkl avatar May 29 '24 06:05 ttkkxfkl

My guess is that this is about connections not properly closed.

T100D avatar Aug 29 '25 08:08 T100D

Have the same issue so far:

E1006 22:10:20.891402 2233531 pinger.go:94] failed to get RX timestamp: no timestamp found
E1006 22:10:20.891402 2233531 pinger.go:94] failed to get RX timestamp: no timestamp found
E1006 22:10:20.891402 2233531 pinger.go:94] failed to get RX timestamp: no timestamp found
E1006 22:10:20.891402 2233531 pinger.go:94] failed to get RX timestamp: no timestamp found

kAleksei avatar Oct 06 '25 22:10 kAleksei