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

calico-node is not running #1225

Open
MikelPan opened this issue Mar 8, 2022 · 3 comments
Open

calico-node is not running #1225

MikelPan opened this issue Mar 8, 2022 · 3 comments
Assignees
Labels
calico kind/bug Something isn't working network

Comments

@MikelPan
Copy link

MikelPan commented Mar 8, 2022

image

2022-03-08 11:52:47.077 [INFO][63] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m3.9s: avg=6ms longest=8ms (resync-nat-v4,resync-raw-v4)
bird: KRT: Received route 10.103.97.2/32 with strange next-hop 10.0.0.15
bird: KRT: Received route 10.103.97.2/32 with strange next-hop 10.0.0.15
bird: KRT: Received route 10.103.97.2/32 with strange next-hop 10.0.0.15

@MikelPan MikelPan added the kind/bug Something isn't working label Mar 8, 2022
@fanux
Copy link
Collaborator

fanux commented Mar 9, 2022

Show you network interface ifconfig

@fanux
Copy link
Collaborator

fanux commented Mar 9, 2022

@bxy4543 this maybe caused by the router module

@k86td
Copy link

k86td commented Nov 1, 2023

@fanux can you provide more details? I might be hitting this.

Updating this for future references. In my case, the Pods weren't running because of a misconfiguration with containerd resulting in (sometimes) Bird losing connections. Result: liveness check restart the Pod and we're stuck in a crash loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
calico kind/bug Something isn't working network
Projects
None yet
Development

No branches or pull requests

5 participants