Help Center/ CodeArts Check/ FAQs/ General Issues/ Why Am I Seeing Error CC.00040010.400?/ Sonarqube Engine Check Failure: elasticSearch Fails to Be Started
Updated on 2026-08-10 GMT+08:00
Sonarqube Engine Check Failure: elasticSearch Fails to Be Started
Symptom
elasticSearch fails to be started: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535].
Cause Analysis
The number of files that can be opened by a process at the same time is too small.
Solution
- Log in to the executor where the check task is executed as the root user.
- Run the following commands to check the number of files that can be opened:
ulimit -Hn ulimit -Sn
- Run the vim /etc/security/limits.conf command to open the file.
- Add the following configuration commands. The configuration takes effect after you log out and log in again.
* soft nofile 65536 * hard nofile 65536
Note that the command must start with an asterisk (*).
- Press Esc to return to the common mode.
- Enter :wq to save and exit.
- Run the following commands to check whether the number of files that can be opened is changed to 65536:
ulimit -Hn ulimit -Sn
Parent topic: Why Am I Seeing Error CC.00040010.400?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot