[PIM] Linux server syslog issue.

Products

• CA Privileged Identity Management Endpoint (PIM)

Issue/Introduction

OS : RHEL 7.4
PIM : 12.81.0.3073

A syslog such as a picture occurs on the Linux server.
I want to know the exact cause and reason for the message.

kernel: [<ffffffff816ae7c8>] dump_stack+0x19/0x180
kernel: [<ffffffff8118cd10>] warn_alloc_fai1ed+0x110/0x180
kernel: [<ffffffff810Fd773>) ? on_each_cpu_mask+0x53/0x70
kernel: [<ffffffff816aa774>] _alloc_pages_s lowpath+0x6b6/0x724
kernel: [<ffffffff811912a5>] _alloc_pages_nodemask+0x405/0x420
kernel: [<ffffffff811d5a38>] alloc_pages_current+0x98/0x110
kernel: [<ffffffff8118bb0e>] __get_free_pages+0xe/0x40
kernel: [<ffffffff811e146e>] kmalloc_order_trace+0x2e/Oxa0
kernel: [<ffffffff81210F28>] ? inode _permission+0x18/0x50 
kernel: [<ffffffff811e5011>] __kmalloc+0x211 /0x230
kernel: [<ffffffffc09808d>] eAC_calloc+0x4d/0x160 [seos]
kernel: [<ffffffffc09d72f4>] SEOS_procserver_show_0e4/0x3d0 [seos]
kernel: [<ffffffff81213803>] ? path_lookupat+0x83/0x7c0
kernel: [<ffffffff8121493d>] ? do_last+0x66d/0x12c0
kernel: [<ffffffffc09cbc84>] SEOS_syscall_v1+0x66d/0x800 [seos]
kernel: [<ffffffffc09b5326>] _SEOS_syscall_+0x416/0x490 [seos]
kernel: [<ffffffffc09bf753>] SEOS_vsysc_ioctl+0xd3/0x160 [seos]
kernel: [<ffffffff8127553d>] proc_reg_unlocked_ioctl+0x3d/0x80
kernel: [<ffffffff81219e90>] do_vfs_ioctl+0x350/0x56
kernel: [<ffffffffc09d81e3>] ? eac_cfree+0x43/0x1f0 [seos]
kernel: [<ffffffffc09bed4c>] ? SEOS_scm_decrement+0xec/0x150) [seos] 
kernel: [<ffffffff8121a141>] syS_ioct 1+0xal/0xc0
kernel: [<ffffffff816C0715>] system_call_fastpath+0x1c/0x21
kernel: Mem-Info:
kernel: active_anon:43574304

Attached is the image.

Environment

Release : 12.8

Component : CA ControlMinder - Unix

Cause

During the execution of the secons command, it tried to allocate memory and got the "page allocation failure: order 7" error message.  This means it tried to allocate a chunk of memory of 512K and the system did not have any 512K memory slots left.  At the bottom 1/4, you shall see "lowmem_reserve[] . . ." and the next line shows the number of slots for each slot size.  For 512K slot, it has 0 slots left. This means either the problematic system did not have sufficient memory to start with or the memory was so fragmented that it could no longer find memory.  This is a system issue, not a PIM issue.

Resolution

This is not a PIM issue, please look at increasing the Physical memory to the system and also perform regular housekeeping activities on the server hosting PIM application.