karaf process killed by OS due to OOM condition
(NETVIRT-974)
|
|
| Status: | Verified |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Jamo Luhrsen |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
In order to get a better understanding of what is going on in the parent issue, and eventually be able to solve it, our first goal should be to confirm for sure that ODL indeed does get terminated by the Kernel OOM killer (and not, say, some obscure JVM bug or something). Apparently the Kernel OOM killer would lead to this Kernel log: host kernel: Out of Memory: Killed process 1234 (java). Could we make sure and get confirmation that this was seen? |
| Comments |
| Comment by Jamo Luhrsen [ 03/Nov/17 ] |
|
doesn't this confirm it: https://jira.opendaylight.org/secure/attachment/14207/dmesg.log.txt |
| Comment by Michael Vorburger [ 03/Nov/17 ] |
|
I hadn't seen the dmesg.log.txt attached to the parent, it clearly does show it is the Kernel OOM killer, here: Out of memory: Kill process 11530 (java) score 934 or sacrifice child Killed process 11530 (java) total-vm:9347296kB, anon-rss:3614460kB, file-rss:0kB, shmem-rss:0kB |
[NETVIRT-975]