linux-oom-analyzer

To diagnose a Linux OOM killer event, analyze kernel logs, process memory snapshots, and cgroup metrics to identify memory pressure indicators. This automated diagnostic path correlates exit code 137 crashes with system-wide pressure, process leaks, or container limits to determine a definitive root cause.

A container crash with exit code 137 indicates the OOM killer triggered due to memory exhaustion. Analyze cgroup metrics and memory snapshots to determine if the cause is a misconfigured cgroup limit or an application memory leak that breached container boundaries.

Yes, you can use Ansible to automate the execution of system diagnostic scripts required to extract and interpret memory pressure indicators. This setup analyzes kernel-space slab or shmem anomalies and routes them to the correct diagnostic workflow.

The best way to troubleshoot a process-specific memory leak is to correlate OOM killer logs with process memory growth trends. Automated scenario routing isolates whether system-wide pressure originates from specific process leaks, container limits, or kernel-space anomalies.

Yes, OOM diagnosis requires access to system diagnostic scripts to extract and interpret memory pressure indicators and OOM killer event data. These scripts gather the kernel logs and cgroup metrics needed to generate standardized, evidence-based diagnostic reports.

You should not use automated memory exhaustion diagnosis if you cannot provide the required system diagnostic scripts or Ansible access. Without these dependencies, the tool cannot extract the kernel logs, cgroup metrics, or memory snapshots needed to interpret OOM killer events.