Memory allocation failure when calling scanCache init()

Technical Articles ID: KB92204
Last Modified: 2022-05-09 05:14:47 Etc/GMT

Environment

Endpoint Security for Linux Threat Prevention (ENSLTP) 10.6.0

Problem

You see the following message recorded in the syslog (in /var/log/messages). A line containing [fileaccess_mod] and [scanCache_init] appears in the call trace:

Nov 6 20:03:02 hostname kernel: FILEACCESS_ERROR : Failed to create mempool memory for scan cache record
Nov 6 20:03:02 hostname kernel: FILEACCESS_ERROR : Failed to restart event processing services.
Nov 6 20:27:10 hostname kernel: Command for FM: page allocation failure: order:7, mode:0x3040d0
Nov 6 20:27:10 hostname kernel: CPU: 1 PID: 7646 Comm: Command for FM Tainted: G OE ------------ 3.10.0-327.73.1.el7.x86_64 #1
Nov 6 20:27:10 hostname kernel: Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/21/2015
Nov 6 20:27:10 hostname kernel: Call Trace:
Nov 6 20:27:10 hostname kernel: [<ffffffff8164731d>] dump_stack+0x19/0x1b
Nov 6 20:27:10 hostname kernel: [<ffffffff81177190>] warn_alloc_failed+0x110/0x180
Nov 6 20:27:10 hostname kernel: [<ffffffff81179b76>] ? drain_local_pages+0x16/0x20
Nov 6 20:27:10 hostname kernel: [<ffffffff8164273c>] __alloc_pages_slowpath+0x69d/0x70b
Nov 6 20:27:10 hostname kernel: [<ffffffff8117b370>] __alloc_pages_nodemask+0x400/0x420
Nov 6 20:27:10 hostname kernel: [<ffffffff81643550>] kmalloc_large_node+0x60/0x8d
Nov 6 20:27:10 hostname kernel: [<ffffffff811ccbc2>] __kmalloc_node+0x222/0x280
Nov 6 20:27:10 hostname kernel: [<ffffffff811742d1>] ? mempool_create_node+0x51/0x140
Nov 6 20:27:10 hostname kernel: [<ffffffff81173ff0>] ? mempool_kfree+0x10/0x10
Nov 6 20:27:10 hostname kernel: [<ffffffff811742f2>] mempool_create_node+0x72/0x140
Nov 6 20:27:10 hostname kernel: [<ffffffff81174010>] ? mempool_alloc_slab+0x20/0x20
Nov 6 20:27:10 hostname kernel: [<ffffffff811743da>] mempool_create+0x1a/0x20
Nov 6 20:27:10 hostname kernel: [<ffffffffa04a4e8c>] scanCache_init+0x7c/0x240 [fileaccess_mod_1005031646]
Nov 6 20:27:10 hostname kernel: [<ffffffffa049d2e5>] PF_setRestartServicesFlag+0xe5/0x150 [fileaccess_mod_1005031646]
Nov 6 20:27:10 hostname kernel: [<ffffffff81253e10>] proc_reg_write+0x40/0x80
Nov 6 20:27:10 hostname kernel: [<ffffffff811e8840>] vfs_write+0xc0/0x1f0
Nov 6 20:27:10 hostname kernel: [<ffffffff811e92ef>] SyS_write+0x7f/0xe0
Nov 6 20:27:10 hostname kernel: [<ffffffff81659055>] system_call_fastpath+0x1c/0x21

Cause

This message displays when the ENSLTP kernel module (fileaccess_mod) fails to allocate continuous memory space. The following are the main causes for memory allocation failure:

The environment uses ENSLTP 10.6.0.
The system has insufficient free memory.
There's free memory in the system, but continuous memory area can't be secured due to fragmentation.

Solution

This issue is resolved in ENSLTP 10.6.1.

Our product software, upgrades, maintenance releases, and documentation are available on the Product Downloads site.

NOTE: You need a valid Grant Number for access. See KB56057 - How to download product updates and documentation for more information about the Product Downloads site, and alternate locations for some products.

Workaround

Restart the system. The fileaccess_mod kernel module requires continuous memory in the kernel for the scan cache store for faster scan cache traversal.

If you see these messages with ENSLTP 10.6.1 and later, even though there's free memory in the Linux system, the memory might be fragmented. Memory fragmentation is eliminated by restarting the system. Contact your Linux operating system vendor for information about how to eliminate or reduce memory fragmentation.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Memory allocation failure when calling scanCache init()

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

Memory allocation failure when calling scanCache init()

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title