You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elasticsearch is not able to start because max file descriptors is too low :
elasticsearch_1 | [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]
Issue related here : docker-library/elasticsearch#140
Environment
Opencti on Centos 7 running into LXC
Reproducible Steps
Steps to create the smallest reproducible scenario:
get a node with # ulimit -n
4096
follow the docker install documentation sysctl -w vm.max_map_count=262144
start # docker-compose up
Actual Output
Elasticsearch docker is restarting in loop with error following elasticsearch_1 | [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]
Additional information
if you increase the ulimit on the pod, it works
# ulimit -n
65535
I don't know if it's better to add a check to have a large ulimit nofile on the documentation or to change the docker-compose.yml with something like on elasticsearch service :
ulimits:
nofile:
soft: 65536
hard: 65536
The text was updated successfully, but these errors were encountered:
Description
Elasticsearch is not able to start because max file descriptors is too low :
elasticsearch_1 | [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]
Issue related here : docker-library/elasticsearch#140
Environment
Reproducible Steps
Steps to create the smallest reproducible scenario:
4096
Actual Output
Elasticsearch docker is restarting in loop with error following
elasticsearch_1 | [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]
Additional information
if you increase the ulimit on the pod, it works
I don't know if it's better to add a check to have a large ulimit nofile on the documentation or to change the docker-compose.yml with something like on elasticsearch service :
The text was updated successfully, but these errors were encountered: