Openshift node crash because of OOM killed

Solution Verified - Updated -

Issue

  • Openshift node crash because of OOM killed
  • Common issues were pods and processes being OOM killed.
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel: Call Trace:
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  dump_stack+0x5c/0x80
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  dump_header+0x4a/0x1db
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  oom_kill_process.cold.32+0xb/0x10
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  out_of_memory+0x1ab/0x4a0
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  mem_cgroup_out_of_memory+0xe8/0x100
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  try_charge+0x65a/0x690
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  mem_cgroup_charge+0xca/0x220
Apr 28 00:25:53 ham-lhtcloud-worker009 kernel:  __add_to_page_cache_locked+0x368/0x3d0

Environment

  • Red Hat Openshift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content