Documentation ¶
Index ¶
Constants ¶
View Source
const ( // e.g., // Out of memory: Killed process 123, UID 48, (httpd). // [...] Out of memory: Killed process 123, UID 48, (httpd). // // NOTE: this is often followed by a line like: // [Sun Dec 8 09:23:39 2024] oom_reaper: reaped process 345646 (vector), now anon-rss:0kB, file-rss:0kB, shmem-rss:0 // (to reap the memory used by the OOM victim) RegexOOM = `Out of memory:` // e.g., // oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null), // [...] oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null), RegexOOMKillConstraint = `oom-kill:constraint=` // e.g., // postgres invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=0 // [...] postgres invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=0 RegexOOMKiller = `(?i)\b(invoked|triggered) oom-killer\b` // e.g., // Memory cgroup out of memory: Killed process 123, UID 48, (httpd). // [...] Memory cgroup out of memory: Killed process 123, UID 48, (httpd). RegexOOMCgroup = `Memory cgroup out of memory` // May indicate that Dual Inline Memory Module (DIMM) is beginning to fail. // // e.g., // [...] EDAC MC0: 1 CE memory read error // [...] EDAC MC1: 128 CE memory read error on CPU_SrcID#1_Ha#0_Chan#1_DIMM#1 // // ref. // https://serverfault.com/questions/682909/how-to-find-faulty-memory-module-from-mce-message // https://github.com/Azure/azurehpc/blob/2d57191cb35ed638525ba9424cc2aa1b5abe1c05/experimental/aks_npd_draino/npd/deployment/node-problem-detector-config.yaml#L51C20-L51C40 RegexEDACCorrectableErrors = `.*CE memory read error.*` )
Variables ¶
This section is empty.
Functions ¶
func HasOOM ¶
Returns true if the line indicates that the file-max limit has been reached. ref. https://docs.kernel.org/admin-guide/sysctl/fs.html#file-max-file-nr
func HasOOMCgroup ¶
func HasOOMKillConstraint ¶
func HasOOMKiller ¶
Types ¶
This section is empty.
Click to show internal directories.
Click to hide internal directories.