OOMKilled

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

 docker inspect grafana | grep -i OOM
           "OOMKilled": false,
           "OomScoreAdj": 0,
           "OomKillDisable": false, 

Related

• Pod The node had condition:
• kubectl get events -A: OOMKilling
• error Command failed with exit code 137
• BackoffLimitExceeded
• kube-proxy --oom-score-adj
• docker inspect XXXX | grep -i mem
• Killed process
• oom_reaper
• kubectl get pods

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, CrashLoopBackOff
• OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s), systemd-oomd, OOMKilled, oom-killer, memcpy, sar -r, Exit code: 137, Killed process, oom_reaper, oom_score_adj