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

RX timestamp: no timestamp found #90

Open
ttkkxfkl opened this issue May 29, 2024 · 1 comment
Open

RX timestamp: no timestamp found #90

ttkkxfkl opened this issue May 29, 2024 · 1 comment

Comments

@ttkkxfkl
Copy link

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
Copy link
Author

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

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

1 participant