Bound or publishing to a non-loopback or non-link-local address


(Hugh McBride) #1

I am having a real tricky time getting the simplest of nodes running. I have the following two configs ( they were copied from another cluster running in the company and the appropriate parts changed )

node 1

cluster.name: "es-bigdata"
network.host: myfqdn1.co.uk
http.port: 9200
transport.tcp.port: 9300
node.name: ${HOSTNAME}-UAT
path.data: "/local/portfolio-apps/elastic/elasticdata"
path.logs: "/local/portfolio-apps/elastic/elasticlogs"
discovery.zen.ping.unicast.hosts: ["myfqdn1.co.uk:9300", "myfqdn2.co.uk:9300"]

node 2

cluster.name: "es-bigdata"
network.host: myfqdn2.co.uk
http.port: 9200
transport.tcp.port:9300
node.name: ${HOSTNAME}-UAT
path.data: "/local/portfolio-apps/elastic/elasticdata"
path.logs: "/local/portfolio-apps/elastic/elasticlogs"
discovery.zen.ping.unicast.hosts: ["myfqdn1.co.uk:9300", "myfqdn2.co.uk:9300"]

I keep getting
bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks

getting the standard loop back error

This is my first foray with ES and it has not been pleasant . Have I missed something in the above configs .

I see the 9200 and 9300 increment by one for every node in the cluster and also stay the same . Is there a good doc / guideline on this

any pointers welcome

hmb

I


(David Pilato) #2

Please format your code using </> icon as explained in this guide. It will make your post more readable.

Or use markdown style like:

```
CODE
```

Please read https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html


(Hugh McBride) #3

It looks pretty readable as is . if you have nothing to contribute then don't add to the chatter .


(David Pilato) #4

Did read my full answer? Including the last link I pasted?


(system) #5

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