Difference between revisions of "Back-off restarting failed container (BackOff)"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
[[kubectl describe pod]] your-pod | [[kubectl describe pod]] your-pod | ||
Warning BackOff 3m20s (x34 over 8m21s) [[kubelet]] [[Back-off restarting failed container]] | Warning BackOff 3m20s (x34 over 8m21s) [[kubelet]] [[Back-off restarting failed container]] | ||
| + | |||
| + | |||
| + | [[kubectl get events]] | ||
| + | your_namespace 30m Warning [[BackoffLimitExceeded]] [[job/]]your-job27740460 Job has reached the specified [[backoff]] limit | ||
| + | |||
| + | |||
Revision as of 05:49, 29 September 2022
kubectl get events -A Warning BackOff 1s (x9 over 95s) kubelet Back-off restarting failed container
kubectl describe pod your-pod Warning BackOff 3m20s (x34 over 8m21s) kubelet Back-off restarting failed container
kubectl get events your_namespace 30m Warning BackoffLimitExceeded job/your-job27740460 Job has reached the specified backoff limit
Back-off restarting failed container Job has reached the specified backoff limit
Related
See also
- Kubernetes events, Kubernetes node events:
[ Normal | Warning ],kubectl events, kubectl get events:BackOff,FailedMount, FailedAttachVolume, TaintManagerEviction, InvalidDiskCapacity,FailedScheduling, kubectl describe events, Unhealthy,conditions:, UpdatedLoadBalancer, BackoffLimitExceeded - K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK - Kubernetes monitoring, node conditions, Kube-state-metrics (KSM), Prometheus, VictoriaMetrics,
node-problem-detector, Thanos, log collection,ProbeWarning, Kubernetes node-problem-detector, Pixie, OpenMetrics,kind: PodMonitor, Jaeger
Advertising:
