Difference between revisions of "Exit code: 137"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | |||
| − | * [[Reason: OOMKilled - exit code: 137]] | + | * <code>[[Reason: OOMKilled - exit code: 137]]</code> |
| − | * [[error Command failed with exit code 137.]] | + | * <code>[[error Command failed with exit code 137.]]</code> |
== Related == | == Related == | ||
Latest revision as of 10:09, 7 December 2023
Related[edit]
See also[edit]
- 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, Killed process,oom_reaper
Advertising:
