ES5.2 - Can't bind to

I'm using ES 5.2 on ubuntu 14.04

My yml contains:
http.port: 9200
transport.tcp.port: 9300

From the log the publish_address is the correct one:,
but the bound_addressed is wrong: [::]:9300, I need it to be

Here is the log:
initializing ...
using [1] data paths, mounts [[/ (/dev/sda1)]], net usable_space [85.6gb], net total_space [102.8gb], spins? [possibly], types [ext4]
heap size [15.9gb], compressed ordinary object pointers [true]
node name [myNodeName_elastic_5], node ID [MdjfQYkkSOGoFafhNQbOGA]
version[5.2.1], pid[3616], build[db0d481/2017-02-09T22:05:32.386Z], OS[Linux/4.4.0-64-generic/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_121/25.121-b13]
loaded module [aggs-matrix-stats]
loaded module [ingest-common]
loaded module [lang-expression]
loaded module [lang-groovy]
loaded module [lang-mustache]
loaded module [lang-painless]
loaded module [percolator]
loaded module [reindex]
loaded module [transport-netty3]
loaded module [transport-netty4]
no plugins loaded
starting ...
publish_address {}, bound_addresses {[::]:9300}
bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
2017-03-08 12:19:18.012066500 ERROR: bootstrap checks failed
2017-03-08 12:19:18.012068500 max file descriptors [32000] for elasticsearch process is too low, increase to at least [65536]
stopping ...
closing ...

(* the "max file descriptors" Error is not the reason because that with other yml the service is find)

Any ideas ?


1 Like

Hi @idanhagai,

This is being caused by bootstrap test failure. The bootstrap checks are run when ES detects that it is in "production mode", as opposed to "development mode".

In this case, attempting to bind to triggered ES to run in production mode.
Take a look at this page that tells how to put ES in production mode.

See here for info about setting the max file descriptors


I increased the file description to 65536 and problem solved :sweat_smile:

1 Like

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