Difference between revisions of "OOMKilled"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
* <code>[[kubectl get events]]</code>: <code>[[OOMKilling]]</code> | * <code>[[kubectl get events]]</code>: <code>[[OOMKilling]]</code> | ||
* <code>[[error Command failed with exit code 137]]</code> | * <code>[[error Command failed with exit code 137]]</code> | ||
| + | * [[BackoffLimitExceeded]] | ||
== See also == | == See also == | ||
Revision as of 11:38, 28 September 2022
Reason:Reason: OOMKilled - exit code: 137 Started at: 2022-08-10T14:04:29+02:00 Finished at: 2022-08-10T14:04:54+02:00
lastState:
terminated:
exitCode: 137
reason: OOMKilled
startedAt: '2022-09-28T11:28:17Z'
finishedAt: '2022-09-28T11:28:31Z'
containerID: >-
docker://d941e84827XXXXX26070d0ab5e29c
Related
Pod The node had condition:kubectl get events:OOMKillingerror Command failed with exit code 137- BackoffLimitExceeded
See also
- OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s),
systemd-oomd, OOMKilled, oom-killer, memcpy,sar -r,Exit code: 137
Advertising:
