Bootstrap check failure [1] of [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]

SonarQube 9.0 on AWS EC2 Instance deployed via CloudFormation Template.

Error message:

bootstrap check failure [1] of [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]

This is recieved when using the environment variables below in my CloudForm template to connect to a AWS RDS Postgres Database.

sudo docker run -d --name sonarqube -p 80:9000 -e SONAR_JDBC_URL=jdbc:postgresql://sonarqubedb.xxxxxxxxxxxx.ap-southeast-2.rds.amazonaws.com:5432/sonarqubedb -e SONAR_JDBC_USERNAME=sonar -e SONAR_JDBC_PASSWORD=xxxxxxxxxxxxxxxx -v sonarqube_data:/opt/sonarqube/data -v sonarqube_extensions:/opt/sonarqube/extensions -v sonarqube_logs:/opt/sonarqube/logs sonarqube:latest

Have run the commands and made the adjustments to the /etc/security/limits.conf file as suggested in the SonarQube 9.0 Requirements.

https://docs.sonarqube.org/latest/requirements/requirements/

sysctl -w vm.max_map_count=524288
sysctl -w fs.file-max=131072
ulimit -n 131072
ulimit -u 8192
sonarqube   -   nofile   131072
sonarqube   -   nproc    8192

Any help getting this up and running with the Postgres configuration would be appreciated.

Hi Jared

Welcome to the community.

Sharing specific code doing the intentions you describe would help me to help you. Please share the code of your scripts or templates where you change the file descriptors limit for the running user — either directly via the shell, and/or indirectly by editing the .conf files and applying that change.


Regards,

I was also got same issue added above perameters not resolved the issue. Can u please suggest me

ERROR: bootstrap check failure [1] of [1]: max file descriptors [8192] for elasticsearch process is too low, increase to at least [65535]

added lines in /etc/security/limits.conf file

sonarqube - nofile 131072
sonarqube - nproc 8192

FYI sonarqube version is --sonarqube-9.9.0.65466
pgsql is 13.2