ElasticSearch error bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks

I am trying to run Elasticsearch 5.4.0 on CentOS 7 on VM

in elasticsearch.yml i have added the below line

network.host: ["192.168.X.Y", "localhost"]

The above IP address belongs to VM not of host OS, without adding the above line it starts fine.

After adding the above link Elasticsearch is not starting and giving the below error.

[2017-05-26T18:06:59,848][INFO ][o.e.t.TransportService   ] [node_uat_master] publish_address {192.168.X.Y:9300}, bound_addresses {127.0.0.1:9300}, {[::1]:9300}, {192.168.X.Y:9300}
[2017-05-26T18:06:59,865][INFO ][o.e.b.BootstrapChecks    ] [node_uat_master] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
ERROR: bootstrap checks failed
max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Increase these params on OS and it resolve your problema

max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

1 Like

Thanks, what is the solution for the above error, I am running Elasticsearch on CentOS 7 on VM

max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]

Solved the above error by changing /etc/security/limit.conf file
by changing these values

*    soft    nofile 65536
*    hard   nofile 65536
# End of file

max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

for above error please check this page https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html

from the above link running the command worked for me but changing the file didn't work (i don't know why)

**Remember to take backup before modifying any file and also login with root

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.