# Bootstrap checks keeps failing **URL:** \ **Category:** Elasticsearch\ **Created:** [February 26, 2020, 12:21pm UTC](https://discuss.elastic.co/t/bootstrap-checks-keeps-failing/221037 "2020-02-26T12:21:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![oengel](https://avatars.discourse-cdn.com/v4/letter/o/bcef8e/32.png) [@oengel](https://discuss.elastic.co/u/oengel)\ **Post date:** [February 26, 2020, 12:21pm UTC](https://discuss.elastic.co/t/bootstrap-checks-keeps-failing/221037/1 "2020-02-26T12:21:46Z")
Hi to all, Im facing issues starting up my Elasticsearch cluster. We have an active-stdby architecture that we manage on our own. So, before im running the elasticsearch, im modifying (runtime) it's configuration on each node. one is set with master=True, and the other with master=False. We have a constant ip to each container, and a constant ip to the active container. the configuration for the master node is as seen below > bootstrap.memory\_lock: true > cluster.initial\_master\_nodes: ["${EXT\_HOSTNAME}"] > cluster.name: dn-elasticsearch > #discovery.seed\_hosts: [10.254.1.7:9300] > http.host: 10.254.1.7 > http.bind\_host: 0.0.0.0 > http.port: ${ELASTICSEARCH\_PORT} > indices.memory.index\_buffer\_size: 512mb > indices.memory.min\_index\_buffer\_size: 32mb > network.publish\_host: 10.254.1.7 > network.bind\_host: 0.0.0.0 > node.data: true > node.ingest: true > node.master: true > node.name: ${EXT\_HOSTNAME} > path.data: /techsupport > path.repo: /elasticsearch\_backup > transport.host: 10.254.1.7 > transport.bind\_host: 0.0.0.0 > transport.port: 9300 the bootstrap check keeps failing no matter what im doing.. > {"type": "server", "timestamp": "2020-02-26T12:11:15,066Z", "level": "INFO", "component": "o.e.d.DiscoveryModule", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "using discovery type [zen] and seed hosts providers [settings]" } > {"type": "server", "timestamp": "2020-02-26T12:11:15,924Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "initialized" } > {"type": "server", "timestamp": "2020-02-26T12:11:15,924Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "starting ..." } > {"type": "server", "timestamp": "2020-02-26T12:11:16,042Z", "level": "INFO", "component": "o.e.t.TransportService", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "publish\_address {10.254.1.7:9300}, bound\_addresses {0.0.0.0:9300}" } > {"type": "server", "timestamp": "2020-02-26T12:11:16,142Z", "level": "INFO", "component": "o.e.b.BootstrapChecks", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "bound or publishing to a non-loopback address, enforcing bootstrap checks" } > ERROR: [3] bootstrap checks failed > [1]: initial heap size [4294967296] not equal to maximum heap size [17179869184]; this can cause resize pauses and prevents mlockall from locking the entire heap > [2]: max file descriptors [64000] for elasticsearch process is too low, increase to at least [65535] > [3]: memory locking requested for elasticsearch process but memory is not locked > {"type": "server", "timestamp": "2020-02-26T12:11:16,151Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "stopping ..." } > {"type": "server", "timestamp": "2020-02-26T12:11:16,177Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "stopped" } > {"type": "server", "timestamp": "2020-02-26T12:11:16,177Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "closing ..." } > {"type": "server", "timestamp": "2020-02-26T12:11:16,187Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dn-elasticsearch", "node.name": "dn55-ncc0", "message": "closed" } can someone please help me figure out what am I doing wrong? best regards, Oded ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [February 26, 2020, 12:24pm UTC](https://discuss.elastic.co/t/bootstrap-checks-keeps-failing/221037/2 "2020-02-26T12:24:22Z")
The problems you need to address are spelled out in detail in this log message: > [@oengel](#): > > ```plaintext > ERROR: [3] bootstrap checks failed > [1]: initial heap size [4294967296] not equal to maximum heap size [17179869184]; this can cause resize pauses and prevents mlockall from locking the entire heap > [2]: max file descriptors [64000] for elasticsearch process is too low, increase to at least [65535] > [3]: memory locking requested for elasticsearch process but memory is not locked > > ``` ---
**Author:** ![oengel](https://avatars.discourse-cdn.com/v4/letter/o/bcef8e/32.png) [@oengel](https://discuss.elastic.co/u/oengel)\ **Post date:** [February 26, 2020, 12:26pm UTC](https://discuss.elastic.co/t/bootstrap-checks-keeps-failing/221037/3 "2020-02-26T12:26:55Z")
damn, im stupid. I was sure if failed due to my network configuration and those are just non-related errors. thank you very much. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 25, 2020, 12:27pm UTC](https://discuss.elastic.co/t/bootstrap-checks-keeps-failing/221037/4 "2020-03-25T12:27:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.