1oomkill(8) System Manager's Manual oomkill(8)
2
3
4
6 oomkill - Trace oom_kill_process(). Uses Linux eBPF/bcc.
7
9 oomkill
10
12 This traces the kernel out-of-memory killer, and prints basic details,
13 including the system load averages at the time of the OOM kill. This
14 can provide more context on the system state at the time: was it get‐
15 ting busier or steady, based on the load averages? This tool may also
16 be useful to customize for investigations; for example, by adding other
17 task_struct details at the time of OOM.
18
19 This program is also a basic example of eBPF/bcc.
20
21 Since this uses BPF, only the root user can use this tool.
22
24 CONFIG_BPF and bcc.
25
27 Trace OOM kill events:
28 # oomkill
29
31 Triggered by ...
32 The process ID and process name of the task that was running
33 when another task was OOM killed.
34
35 OOM kill of ...
36 The process ID and name of the target process that was OOM
37 killed.
38
39 loadavg
40 Contents of /proc/loadavg. The first three numbers are 1, 5, and
41 15 minute load averages (where the average is an exponentially
42 damped moving sum, and those numbers are constants in the equa‐
43 tion); then there is the number of running tasks, a slash, and
44 the total number of tasks; and then the last number is the last
45 PID to be created.
46
48 Negligible.
49
51 This is from bcc.
52
53 https://github.com/iovisor/bcc
54
55 Also look in the bcc distribution for a companion _examples.txt file
56 containing example usage, output, and commentary for this tool.
57
59 Linux
60
62 Unstable - in development.
63
65 Brendan Gregg
66
68 memleak(8)
69
70
71
72USER COMMANDS 2016-02-09 oomkill(8)