Difference between revisions of "Exit code: 137"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
* [[error Command failed with exit code 137.]] | * [[error Command failed with exit code 137.]] | ||
| + | == Related == | ||
| + | * [[Last Status]] | ||
== See also == | == See also == | ||
Revision as of 09:42, 7 December 2023
Pods running in Kubernetes will show a status of OOMKilled when they encounter a 137 exit code.
Related
See also
- 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 - OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s),
systemd-oomd, OOMKilled, oom-killer, memcpy,sar -r,Exit code: 137
Advertising:
