Article ID: 118536, created on Nov 10, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

The following messages are logged in /var/log/messages:

Nov 10 09:02:27 pvc kernel: [2345434.431242] 143187 (httpd) invoked oom-killer in ub 102 generation 10 gfp 0x200d2
Nov 10 09:02:27 pvc kernel: [2345434.431306] RAM: 524071 / 524288 [29] SWAP: 0 / 0 [29] KMEM: 35631104 / inf [0] DCSZ: 23070405 / inf [0] OOMG: 233776 / inf [10] Dirty 585 Wback 0 Dche 23205 Prnd 17841
Nov 10 09:02:27 pvc kernel: [2345434.431583] Out of memory in UB: OOM killed process 143187 (httpd) score 0 vm:484752kB, rss:464124kB, swap:0kB
Nov 10 09:02:28 pvc kernel: [2345434.458442] oom-killer in ub 102 generation 10 ends: task died
Nov 10 09:02:28 pvc kernel: [2345434.458447] RAM: 460247 / 524288 [32] SWAP: 0 / 0 [32] KMEM: 34574336 / inf [0] DCSZ: 23070405 / inf [0] OOMG: 233776 / inf [11] Dirty 585 Wback 0 Dche 23205 Prnd 17841

Answer

Whenever containers hit their memory limits, the OOM killer on the hardware node kills the most memory consuming processes inside the container. The container ID, which experiences memory shortage, is logged in the messages journal. The first line contains the container ID in question: invoked oom-killer in ub 102

Resolution

Increase the memory limits for container as per the following article:

126161 How to set memory limit for containers?

Search Words

OOM killer

cpu load

swap

Out of memory in UB

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF