Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused #9638
Comments
|
calico.zip |
|
@huanghaiqing1 @huangzeqi probably a good next step is to look at the This message - |
|
@huanghaiqing1 @huangzeqi any update on this issue? Have you managed to find the root cause? |
|
I have this issue to. do you have any resolution?? @caseydavenport @huangzeqi @huanghaiqing1 |
|
@tomastigera
|
|
@huanghaiqing1 how resolve this problem.? could you please explain solution if resolved that ? |
|
You can’t use tigera-operator.yaml + custom-resources.yaml to deploy calico. You have to use calico.yaml to deploy. I’m trapped by this for quite a long time. In China, I can’t directly access the image address, so I have to download all images to local private registry hub and change image address inside calico.yaml. Then to deploy. Note: based on the official way: tigera-operator.yaml + custom-resources.yaml, even you change related images address to local registry hub address, still can’t pass[some k8s official pods deployment still require access google/docker.io, I can’t access directly from China]. I guess there are other related yaml files, which are called by tigera-operator.yaml + custom-resources.yaml. But when use all in one yaml: calico.yaml, the issue can be suppressed.
… 2025年2月1日 14:15，mohammadt-github ***@***.***> 写道：
@huanghaiqing1 <https://github.com/huanghaiqing1> how resolve this problem.? could you please explain solution if resolved that ?
—
Reply to this email directly, view it on GitHub <#9638 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHFAPJGIMUWSUHKQAULKUVD2NRRBJAVCNFSM6AAAAABUBGMV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRYHAYDGMJQHE>.
You are receiving this because you were mentioned.
|
|
I can pull all images from any registry, and that's ok. but after a seconds calico pods that deploy in worker (in same network range of Master) restarted and Crashloopbackof... |
|
I too am experiencing the same problem. Has anything been resolved? 🥲 |
|
@mohammadt-github these lines in your logs seem related as @caseydavenport said above, it probably means that confd is encountering issues generating the BIRD configuration files, and as such BIRD is failing to start. Do you have anything else happening earlier in your logs? |
|
Hi! in logs same as above. Маybe can help all logs from pod? |
|
The problem was caused by using duplicate ports. If you don't know, please refer to the port. |
|
no, in my case there is no one, who can listen to this port. root@raspberrypi5-ubuntu1:/home/schizo# ss -nutlp
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("avahi-daemon",pid=731,fd=12))
udp UNCONN 0 0 127.0.0.54:53 0.0.0.0:* users:(("systemd-resolve",pid=549,fd=16))
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=549,fd=14))
udp UNCONN 0 0 192.168.1.201%wlan0:68 0.0.0.0:* users:(("systemd-network",pid=716,fd=24))
udp UNCONN 0 0 0.0.0.0:33315 0.0.0.0:* users:(("avahi-daemon",pid=731,fd=14))
udp UNCONN 0 0 [::]:5353 [::]:* users:(("avahi-daemon",pid=731,fd=13))
udp UNCONN 0 0 [::]:56083 [::]:* users:(("avahi-daemon",pid=731,fd=15))
udp UNCONN 0 0 [fe80::2ecf:67ff:fe31:895e]%wlan0:546 [::]:* users:(("systemd-network",pid=716,fd=26))
tcp LISTEN 0 4096 127.0.0.1:10248 0.0.0.0:* users:(("kubelet",pid=778,fd=15))
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=549,fd=15))
tcp LISTEN 0 4096 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=2927,fd=3),("systemd",pid=1,fd=100))
tcp LISTEN 0 4096 127.0.0.1:45981 0.0.0.0:* users:(("containerd",pid=801,fd=10))
tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* users:(("systemd-resolve",pid=549,fd=17))
tcp LISTEN 0 4096 *:10250 *:* users:(("kubelet",pid=778,fd=14))
tcp LISTEN 0 4096 [::]:22 [::]:* users:(("sshd",pid=2927,fd=4),("systemd",pid=1,fd=101))
|
|
Could this issue be related? #9752 |
|
i'm not sure, but in my case i have similar symptoms. |
|
Here's what I recommend:
|
|
Hi this is my earlier log in pod @coutinhop @caseydavenport root@srv-master1:~# k logs calico-node-srlvt -n kube-system | less |
|
heh. |
|
?? any solution?? |
Setup a ha based k8s and deploy first control plane node with calico, met below warning.
tigera-operator.yaml + custom-resources.yaml are deployed with no error. But IPv4 BGP status reports nothing. calico-node-qcv5g runs but kubectl describe with warning like below shows. And I have no OS level acl/iptables/nft block about any rules. All my environment is based on vmware workstation. Any prerequisite requir3ed about calico?
kubelet Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
The text was updated successfully, but these errors were encountered: