Reboot - UseLargePages - Error upon reboot of vapp - bash: fork cannot allocate memory
search cancel

Reboot - UseLargePages - Error upon reboot of vapp - bash: fork cannot allocate memory

book

Article ID: 248407

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

Enable updated in /etc/sysctl.conf  parameters for UseLargePages

OS of vApp has 32 GB RAM   
IM (Wildfly) has 24 GB RAM as max JVM memory.

We have set the parameter of kernel.shmax=34359738368
And calculated the vm.nr_hugepages = 16384


vApp was rebooted.   We can login with config but have limited access.

bash: fork cannot allocate memory

 

Environment

CA IDENTITY SUITE (VIRTUAL APPLIANCE)

Cause

Caused by lack of RAM. "Hugepages" was miscalculated and set too high at 32 GB (16284 x 2k pages).

 

Resolution

Actions:     Increase ESXi server memory for vApp from 32 GB to 48 GB for four (4) vApp (Wildfly) images.


After a successful reboot, we are able to edit /etc/sysctl.conf to lower the value of hugepages.     



vm.nr_hugepages = 13312    [1024*2048=27917287424  =>  26 GB]

 

Current Specs are now:

OS of vApp:  48 GB         [Increased from 32 GB  -  Perf Env was 64 GB]

Parameters in /etc/sysctl.conf   [Modify outside of the CA Parameter section - otherwise it will rollback upon reboot]

kernel.shmmax = 34359738368    (32 GB)   &   vm.nr_hugepages = 13312      (@ 2MB each =>  26 GB)

IM (Wildfly) Max Memory:  24 GB


Note:  If we increase the JVM max memory beyond 24 GB, we will need to modify the /etc/sysctl.conf parameters.

Additional Information

If the system does not allow you to revert changes, have your VM administrator add additional RAM, (temporarily or permanently).