Difference between revisions of "Out of memory"
From Kolmisoft Wiki
Jump to navigationJump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Check logs like this: cat /var/log/messages | grep memory | |||
= Kill process score 10 or sacrifice child = | = Kill process score 10 or sacrifice child = | ||
May 14 17:12:31 sip3-mor kernel: [<ffffffff8111d6b0>] ? out_of_memory+0x220/0x3c0 | |||
May 14 17:12:32 sip3-mor kernel: Out of memory: Kill process 17589 (pcapsipdump) score 10 or sacrifice child | |||
May 14 17:12:38 sip3-mor kernel: [<ffffffff8111d6b0>] ? out_of_memory+0x220/0x3c0 | |||
May 15 07:34:53 sip3-mor kernel: init_memory_mapping: 0000000000000000-00000000c0000000 | |||
Linux is built with a bunch of ‘daemons’. Those daemons are shepherded by several kernel jobs. Apparently all modern Linux kernels have a built-in mechanism called “Out Of Memory killer” which can annihilate your processes under extremely low memory conditions. When such a condition is detected, the killer is activated and picks a process to kill. The target is picked using a set of heuristics scoring all processes and selecting the one with the worst score to kill. | Linux is built with a bunch of ‘daemons’. Those daemons are shepherded by several kernel jobs. Apparently all modern Linux kernels have a built-in mechanism called “Out Of Memory killer” which can annihilate your processes under extremely low memory conditions. When such a condition is detected, the killer is activated and picks a process to kill. The target is picked using a set of heuristics scoring all processes and selecting the one with the worst score to kill. | ||
Source: https://plumbr.eu/blog/memory-leaks/out-of-memory-kill-process-or-sacrifice-child | * Source: https://plumbr.eu/blog/memory-leaks/out-of-memory-kill-process-or-sacrifice-child | ||
More Info: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/s-memory-captun.html | * More Info: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/s-memory-captun.html | ||
Solution: find a process which depletes your RAM and fixed it. Or add more RAM. | Solution: find a process which depletes your RAM and fixed it. Or add more RAM. | ||
Latest revision as of 07:56, 16 May 2016
Check logs like this: cat /var/log/messages | grep memory
Kill process score 10 or sacrifice child
May 14 17:12:31 sip3-mor kernel: [<ffffffff8111d6b0>] ? out_of_memory+0x220/0x3c0 May 14 17:12:32 sip3-mor kernel: Out of memory: Kill process 17589 (pcapsipdump) score 10 or sacrifice child May 14 17:12:38 sip3-mor kernel: [<ffffffff8111d6b0>] ? out_of_memory+0x220/0x3c0 May 15 07:34:53 sip3-mor kernel: init_memory_mapping: 0000000000000000-00000000c0000000
Linux is built with a bunch of ‘daemons’. Those daemons are shepherded by several kernel jobs. Apparently all modern Linux kernels have a built-in mechanism called “Out Of Memory killer” which can annihilate your processes under extremely low memory conditions. When such a condition is detected, the killer is activated and picks a process to kill. The target is picked using a set of heuristics scoring all processes and selecting the one with the worst score to kill.
- Source: https://plumbr.eu/blog/memory-leaks/out-of-memory-kill-process-or-sacrifice-child
- More Info: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/s-memory-captun.html
Solution: find a process which depletes your RAM and fixed it. Or add more RAM.
