栏目分类:
子分类:
返回
名师互学网用户登录
快速导航关闭
当前搜索
当前分类
子分类
实用工具
热门搜索
名师互学网 > IT > 系统运维 > 运维 > Linux

k8s nginx-ingress crashbackoff

Linux 更新时间: 发布时间: IT归档 最新发布 模块sitemap 名妆网 法律咨询 聚返吧 英语巴士网 伯小乐 网商动力

k8s nginx-ingress crashbackoff

今天线上打镜像发现编译机出问题了,查看了pod发现k8s的nginx-ingress一直在crash,于是查看了日志,发现一直在报:

2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: bind() to 0.0.0.0:80 failed (98: Address already in use)
2022/03/02 02:43:29 [emerg] 36#36: still could not bind()
W0302 02:43:32.515637       7 controller.go:220] Dynamic reconfiguration failed: Post http+unix://nginx-status/configuration/backends: read unix @->/tmp/nginx-status-server.sock: read: connection reset by peer

发现有其他进程占用了80端口,导致nginx-ingress一直绑定不上,最后crash了。
使用命令

sudo netstat -ntlp | grep :80

发现是kube-proxy占用了80端口,那么剩下的问题就简单了,将kube-proxy所在的pod删除就行。

kubectl delete pod kube-proxy-xxxx -n kube-system

相对的如果是其他进程占用了80端口,那么也可以直接kill -9 pid即可

转载请注明:文章转载自 www.mshxw.com
本文地址:https://www.mshxw.com/it/752510.html
我们一直用心在做
关于我们 文章归档 网站地图 联系我们

版权所有 (c)2021-2022 MSHXW.COM

ICP备案号:晋ICP备2021003244-6号