--------- -------- ----- ---- ------------- -------- ------ ------- 11m 11m 1 {default-scheduler } Normal Scheduled Successfully assigned pod-with-healthcheck to dev-mg4.internal.tude.com 11m 11m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id ee8718fcfa36; Security:[seccomp=unconfined] 11m 11m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id ee8718fcfa36 9m 9m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id 030a5e32e952; Security:[seccomp=unconfined] 9m 9m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id ee8718fcfa36: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 9m 9m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id 030a5e32e952 7m 7m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id 28f81ea65711 7m 7m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id 030a5e32e952: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 7m 7m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id 28f81ea65711; Security:[seccomp=unconfined] 6m 6m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id 28f81ea65711: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 6m 6m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id f186b8dda69c; Security:[seccomp=unconfined] 6m 6m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id f186b8dda69c 4m 4m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id f186b8dda69c: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 4m 4m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id 008a30536782; Security:[seccomp=unconfined] 4m 4m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id 008a30536782 3m 3m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id 030f5bccb32b; Security:[seccomp=unconfined] 3m 3m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id 030f5bccb32b 3m 3m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id 008a30536782: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 1m 1m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id 04046c952761 11m 1m 7 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Pulled Container image "reg.docker.tude.com/cmall/business:test-1-master" already present on machine 1m 1m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id 030f5bccb32b: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 1m 1m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id 04046c952761; Security:[seccomp=unconfined] 10m 40s 9 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Warning Unhealthy Liveness probe failed: HTTP probe failed with statuscode: 404 9s 9s 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id 04046c952761: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 9s 8s 3 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Warning BackOff Back-off restarting failed docker container 9s 8s 3 {kubelet dev-mg4.internal.tude.com} Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "nginx" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=nginx pod=pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" 1m 1m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Created Created container with docker id 5c4597fa06b9; Security:[seccomp=unconfined] 15m 1m 8 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Pulled Container image "reg.docker.tude.com/cmall/business:test-1-master" already present on machine 1m 1m 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Started Started container with docker id 5c4597fa06b9 14m 54s 10 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Warning Unhealthy Liveness probe failed: HTTP probe failed with statuscode: 404 23s 23s 1 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Normal Killing Killing container with docker id 5c4597fa06b9: pod "pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)" container "nginx" is unhealthy, it will be killed and re-created. 4m 6s 18 {kubelet dev-mg4.internal.tude.com} spec.containers{nginx} Warning BackOff Back-off restarting failed docker container 23s 6s 4 {kubelet dev-mg4.internal.tude.com} Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "nginx" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=nginx pod=pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)"
apiVersion: v1 kind: Pod metadata: name: pod-with-healthcheck spec: containers: - name: nginx image: reg.docker.tude.com/cmall/business:test-1-master # defines the health checking livenessProbe: # an http probe httpGet: path: /111213asd port: 80 # length of time to wait for a pod to initialize # after pod startup, before applying health checking initialDelaySeconds: 30 timeoutSeconds: 10 # 检查周期 periodSeconds: 30 # 临界值 # successThreshold: 1 # 失败次数报 Unhealthy Liveness probe failed: HTTP probe failed with statuscode: 404,不检测了 , kubernetes-dashboard 出现错误 # failureThreshold: 3 ports: - containerPort: 80
Liveness probe failed: HTTP probe failed with statuscode: 404 Back-off restarting failed docker container Error syncing pod, skipping: failed to "StartContainer" for "nginx" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=nginx pod=pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)"
pod-with-healthcheck
Waiting: CrashLoopBackOff
7
16 minutes
Liveness probe failed: HTTP probe failed with statuscode: 404
Back-off restarting failed docker container
Error
syncing pod, skipping: failed to "StartContainer" for "nginx" with
CrashLoopBackOff: "Back-off 2m40s restarting failed container=nginx
pod=pod-with-healthcheck_default(f298e45a-0089-11e7-a3ad-005056ae01be)"
相关推荐
kubectl proxy --www=path/to/gcp-live-k8s-visualizer --www-prefix=/my-mountpoint/ --api-prefix=/api/ 然后 http://127.0.0.1:8001/my-mountpoint/ 而已。 可视化器使用标签来组织可视化。 特别是它期望 容器...
K8s live-1集群 上有一个暂存环境 暂存环境使用http基本身份验证来限制访问。 用户名和密码应该可以从MoJ Rattic服务器的Family Justice组中获得。 此环境应用于任何测试或演示目的,用户研究等。 不要将生产用于...
Ubuntu-21.10系统下从零开始离线安装 Kubernetes 1.24.3
You will also get a deep understanding of how to scale and update live containers and how to do port forwarding and network routing in Kubernetes. Next, you will learn how to build a robust high ...
Kubernetes,通常简称 k8s,是一个开源容器编排系统,它允许管理和调度容器化应用程序在集群中的运行。kubeCDN 将 Kubernetes 的强大功能与 CDN 的高效内容分发特性相结合,为用户提供了更高的灵活性、可控性和安全...
如果遇到类似问题:`[error]33249#0:*46 no live upstreams while connecting to upstream, client:10.16.21.118, server:myserver`,可以采取以下步骤进行排查: 1. **检查错误日志**:定位到Nginx的错误日志文件,...
在K8S平台上构建PaaS平台,可以实现更高级别的应用管理和发布策略,例如通过Deployment和ReplicaSet进行应用的声明式管理,以及通过自定义资源定义(CRD)扩展发布策略,如CAFEDeployment,实现更精细的灰度发布、...
Kubernetes培训和食谱 该存储库包含有关O'Reilly 在线培训的说明和示例。 日期在培训时间表中列出。 它还包含Kubernetes 使用的。 先决条件 在本培训中,我们将使用运行本地Kubernetes实例。 我们将使用名为kubectl...
灯船 :ship: (请阅读部分。) 抽象化Kubernetes中运行的Node.js服务的就绪性,活动性和启动检查以及正常关闭。... 请参阅以下Kubernetes文档以获取有关准备情况和.../live 端点响应: 200状态码,消息“ SERVER_IS_NOT_
k0otkit:针对K8s集群的通用后渗透控制技术 网络安全等级保护2.0之云计算安全测评指标选取原则 面向实战的云安全体系构建与实践 人工智能与物联网前沿论坛 物流行业物联网安全体系构建及思考 AI模型的现实...
Kubernetes(K8s)等容器编排工具则简化了集群管理和扩展。 总结来说,构建可扩展架构涉及多方面技术和策略的综合运用,包括但不限于系统设计原则、技术选型、最佳实践以及工具的使用。"building-a-scalable-...
11. **Docker与Kubernetes**:Docker容器化技术让应用部署标准化,Kubernetes(K8s)提供了一套强大的集群管理系统,理解其工作原理和YAML配置文件是现代云原生开发的关键。 12. **微服务架构**:理解微服务设计...
该控制器是独立于提供程序的,但是首先我们建议您使用Let's Encrypt( )。 有关更多信息,请参见“。)为您的对象启用ACME证书在集群上运行openshift-acme控制器后,您所需要做的就是注释Route或其他受支持的对象...
在Kubernetes(K8s)集群管理中,资源的有效性和生命周期管理是至关重要的。Kubernetes提供了多种机制来确保集群的高效运行,其中之一就是通过设置TTL(Time-To-Live)来自动清理资源。本篇文章将深入探讨如何在...
入口监控器弃用通知: IMC现在已转换为操作员,尽管我们仍然感谢社区对控制器的支持,但我们已停止为基于控制器的实现提供支持。 建议使用“操作员”,现有用户可以按照“要求迁移到“操作员”。...