How to find LXC ID related to Kernel oom Message

yena

Renowned Member
Nov 18, 2011
373
4
83
Hello,
how can i find the LXC ID related to this kernel oom error ?

hild) c
Sep 15 13:02:59 nodo2 kernel: [1736978.941164] mysqld invoked oom-killer: gfp_mask=0x24000c0, order=0, oom_score_adj=0
Sep 15 13:02:59 nodo2 kernel: [1736978.941168] mysqld cpuset=ns mems_allowed=0-1
Sep 15 13:02:59 nodo2 kernel: [1736978.941173] CPU: 1 PID: 14711 Comm: mysqld Tainted: P O 4.4.49-1-pve #1
Sep 15 13:02:59 nodo2 kernel: [1736978.941174] Hardware name: Supermicro PIO-6027TR-TDRF-LC019/X9DRT, BIOS 3.2a 08/04/2015
Sep 15 13:02:59 nodo2 kernel: [1736978.941175] 0000000000000286 000000005135510c ffff880134e6bc90 ffffffff813fa693
Sep 15 13:02:59 nodo2 kernel: [1736978.941178] ffff880134e6bd68 ffff88104d077c00 ffff880134e6bcf8 ffffffff8120b3ab
Sep 15 13:02:59 nodo2 kernel: [1736978.941180] 0000000000000000 ffff88013a72b680 ffff880126d39c00 ffff880134e6bce8
Sep 15 13:02:59 nodo2 kernel: [1736978.941182] Call Trace:
Sep 15 13:02:59 nodo2 kernel: [1736978.941188] [<ffffffff813fa693>] dump_stack+0x63/0x90
Sep 15 13:02:59 nodo2 kernel: [1736978.941193] [<ffffffff8120b3ab>] dump_header+0x67/0x1d5
Sep 15 13:02:59 nodo2 kernel: [1736978.941197] [<ffffffff81392f9a>] ? apparmor_capable+0x1aa/0x1b0
Sep 15 13:02:59 nodo2 kernel: [1736978.941201] [<ffffffff81192875>] oom_kill_process+0x205/0x3c0
Sep 15 13:02:59 nodo2 kernel: [1736978.941205] [<ffffffff811fef8f>] ? mem_cgroup_iter+0x1cf/0x380
Sep 15 13:02:59 nodo2 kernel: [1736978.941208] [<ffffffff81200f58>] mem_cgroup_out_of_memory+0x2a8/0x2f0
Sep 15 13:02:59 nodo2 kernel: [1736978.941210] [<ffffffff81201cf7>] mem_cgroup_oom_synchronize+0x347/0x360
Sep 15 13:02:59 nodo2 kernel: [1736978.941213] [<ffffffff811fcd20>] ? mem_cgroup_begin_page_stat+0x90/0x90
Sep 15 13:02:59 nodo2 kernel: [1736978.941215] [<ffffffff81192f74>] pagefault_out_of_memory+0x44/0xc0
Sep 15 13:02:59 nodo2 kernel: [1736978.941218] [<ffffffff8106af4f>] mm_fault_error+0x7f/0x160
Sep 15 13:02:59 nodo2 kernel: [1736978.941220] [<ffffffff8106b753>] __do_page_fault+0x3e3/0x410
Sep 15 13:02:59 nodo2 kernel: [1736978.941223] [<ffffffff8106b7a2>] do_page_fault+0x22/0x30
Sep 15 13:02:59 nodo2 kernel: [1736978.941227] [<ffffffff818624b8>] page_fault+0x28/0x30
Sep 15 13:02:59 nodo2 kernel: [1736978.941689] Task in /lxc/92162/ns killed as a result of limit of /lxc/92162
Sep 15 13:02:59 nodo2 kernel: [1736978.941697] memory: usage 8388516kB, limit 8388608kB, failcnt 11610104
Sep 15 13:02:59 nodo2 kernel: [1736978.941699] memory+swap: usage 12582804kB, limit 12582912kB, failcnt 117847639
Sep 15 13:02:59 nodo2 kernel: [1736978.941701] kmem: usage 0kB, limit 9007199254740988kB, failcnt 0
Sep 15 13:02:59 nodo2 kernel: [1736978.941702] Memory cgroup stats for /lxc/92162: cache:0KB rss:0KB rss_huge:0KB mapped_file:0KB di
rty:0KB writeback:0KB swap:0KB inactive_anon:0KB active_anon:0KB inactive_file:0KB active_file:0KB unevictable:0KB
Sep 15 13:02:59 nodo2 kernel: [1736978.941723] Memory cgroup stats for /lxc/92162/ns: cache:5668KB rss:8382756KB rss_huge:0KB mapped
_file:4548KB dirty:0KB writeback:0KB swap:4194304KB inactive_anon:1242576KB active_anon:7144708KB inactive_file:372KB active_file:31
2KB unevictable:0KB


Thanks!
 
yes, it is.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!