Environment

• YugabyteDB Anywhere - All
• Manual Provisioning 
• OnPrem Providers

Issue

Preflight checks fail with the error message: 

 Failed preflight checks for node detached_node. Code: 1. Output: [ {
  "type" : "ULIMIT_OPEN_FILES",
  "valid" : false,
  "required" : true,
  "description" : "Maximum number of open file descriptors",
  "value" : "262144"

Where the key observation is the message: "ULIMIT_OPEN_FILES"

Resolution

Overview

Most operating systems require a reboot or service reload in order otherwise apply specific types of configuration changes. After adjusting the ulimit setting, the server should be restarted to ensure that the new settings take effect. 

Steps

1.  If you have made the appropriate changes you may see the correct values displayed, with the ulimit command, however in the background the value reported in the failure is 262144 or something lower than what is displayed with the output from the command. 

Example ulimit output (with desired values):  

[yugabyte@yb-demo-chamilton-pitr-n1 ~]$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 13746
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1048576
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 12000
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

Verify the value is 1048576 is set for open files.

2. If the value is correctly set to 1048576 , but the check is failing this is because the server needs to be rebooted for the changes to take effect. See step 4. 

3.  If the value is less than 1048576, modify the following files as the root user. Following the instructions in YugabyteDB documentation: https://docs.yugabyte.com/preview/deploy/manual-deployment/system-config/#set-ulimits

4. Reboot the tserver to ensure that the value specified in the previous is properly applied, and persisted across a system restart. The most common method of reboot is to run the following as user root:

reboot

5.  Once the node has rebooted, run the preflight check again. 

Reference: SUPPORT-798