Error from server: Get “https:IP:10250/*“:dial tcp IP:10250: connect: no route to host

Error from server: Get “https://10.23.XX:10250/containerLogs/kpanda-system/kpanda-controller-manager-6c77785f75-htwbd/kpanda-controller-manager”: dial tcp 10.23.XX:10250: connect: no route to host

问题发现：
在集群中部署应用，查看状态，发现某个pod一直起不来。

kubectl get pod -A

问题追踪及解决：
查看该pod的日志发现如下：

kubectl logs $POD -n $NS
Error from server: Get "https://10.23.XX:10250/containerLogs/kpanda-system/kpanda-controller-manager-6c77785f75-htwbd/kpanda-controller-manager": dial tcp 10.23.XX:10250: connect: no route to host

在master节点上ping连接不上的这台主机发现可以ping通：

[root@10-23-xx-xx ~]#  ping node-1
PING node-1 (10.23.75.169) 56(84) bytes of data.
64 bytes from node-1 (10.23.xx.xx): icmp_seq=1 ttl=63 time=1.16 ms
64 bytes from node-1 (10.23.xx.xx): icmp_seq=2 ttl=63 time=0.257 ms
^C
--- node-1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.257/0.592/1.161/0.405 ms

再次检查端口是否打开，发现端口不通：

[root@10-23-xx-xx ~]# telnet 10.23.xx.xx 10250
Trying 10.23.xx.xx...

去该node节点上查看防火墙状态，发现防火墙是开着的，原因找到啦，问题就很好解决了。

[root@10-23-xx-xx ~]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemonLoaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)Active: active (running) since 四 2022-01-20 12:52:25 CST; 1h 6min agoDocs: man:firewalld(1)Main PID: 843 (firewalld)Tasks: 2Memory: 27.2MCGroup: /system.slice/firewalld.service└─843 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid1月 20 12:52:35 10-23-xx-xx firewalld[843]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -D FORWARD -i doc...in?).
1月 20 12:52:35 10-23-75-169 firewalld[843]: WARNING: COMMAND_FAILED:
'/usr/sbin/iptables -w2 -t filter -C FORW...name.
Hint: Some lines were ellipsized, use -l to show in full.
[root@10-23-xx-xx ~]# systemctl stop firewalld
[root@10-23-xx-xx ~]# systemctl disable firewalld
Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service.
Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.

再次查看pod状态，已经正常running。

Error from server: Get “https:IP:10250/*“:dial tcp IP:10250: connect: no route to host相关推荐

Error response from daemon: Get https://xxxx/v2/: dial tcp xxxxx:443: connect: co
错误如图所示: Error response from daemon: Get https://10.226.19.157/v2/: dial tcp 10.226.19.157:443: conne ...
k8s dial tcp connect: no route to host
莫名其妙遇到-pod container 启动失败:Back-off restarting failed container StatefulSet zk 集群 pod 一直处于pending,pv ...
TCP/IP学习笔记:TCP/IP协议介绍
TCP/IP的通讯协议这部分简要介绍一下TCP/IP的内部结构,为讨论与互联网有关的安全问题打下基础.TCP/IP协议组之所以流行,部分原因是因为它可以用在各种各样的信道和底层协议(例如T1和X.2 ...
计算机网络三：域名、IP地址和TCP/IP协议
一.域名域名(Domain Name),简称域名.网域,是由一串用点分隔的字符型标志名字组成的Internet上某一台计算机或计算机组的名称,用于在数据传输时标识计算机的电子方位(有时 ...
dial tcp [::1]:10248: connect: connection refused
k8s加入节点时报错 [root@node2 ~]# kubeadm join 192.168.75.140:6443 --token ap25bk.sodr97gp1w8p01xv --discov ...
PyKMIP-master连接PMIP Server时报错could not open client connection: [Errno 113] No route to host
Pykmip client: 使用pykmip客户端PyKMIP-master脚本验证 kmipserver 是否正常工作: $cd /root/PyKMIP-master/kmip/demos/pi ...
计算机网路基础（IP地址、TCP/IP协议、三握四挥）
IP地址 IP地址分类: A,B,C,D,E A,B,C --- 单播地址 D --- 组播地址 E --- 保留地址 (美国军方自己留的) 单播地址:一对一的通信,可以是位于不同广播域的设备进行交流 ...
HyperTerminal 超级终端设置TCP/IP Client和TCP/IP Server
HyperTerminal是一款很古典的软件了,modem数据交换.文件传送,到后来Telnet和ssh也都能用它,再到后来 TCP/IP socket 也还能用它. 以HyperTerminal 7 ...
TCP/IP详解--TCP/IP中三次握手四次握手状态分析
TCP(Transmission Control Protocol) 传输控制协议 TCP是主机对主机层的传输控制协议,提供可靠的连接服务,采用三次握手确认建立一个连接: 位码即tcp标志位,有6种标 ...

Error from server: Get “https:IP:10250/*“:dial tcp IP:10250: connect: no route to host

Error from server: Get “https:IP:10250/*“:dial tcp IP:10250: connect: no route to host相关推荐

最新文章

热门文章