# Bound or publishing to a non-loopback address, enforcing bootstrap checks **URL:** \ **Category:** Elasticsearch\ **Created:** [September 12, 2019, 2:42pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276 "2019-09-12T14:42:10Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Ersoy\_Vatansever](https://avatars.discourse-cdn.com/v4/letter/e/51bf81/32.png) [@Ersoy\_Vatansever](https://discuss.elastic.co/u/Ersoy_Vatansever)\ **Post date:** [September 12, 2019, 2:42pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/1 "2019-09-12T14:42:10Z")
Hi , i decied to use elastic on linux centos but i cant resolved below issue. I have two servers with same configurations. Elastic works separately but cannot be cluster and i see log below. Elasticsearch version is 7.3.1 [2019-09-12T15:23:22,043][INFO][o.e.p.PluginsService] [node-1] loaded module [percolator] [2019-09-12T15:23:22,043][INFO][o.e.p.PluginsService] [node-1] loaded module [rank-eval] [2019-09-12T15:23:22,044][INFO][o.e.p.PluginsService] [node-1] loaded module [reindex] [2019-09-12T15:23:22,044][INFO][o.e.p.PluginsService] [node-1] loaded module [repository-url] [2019-09-12T15:23:22,045][INFO][o.e.p.PluginsService] [node-1] loaded module [transport-netty4] [2019-09-12T15:23:22,045][INFO][o.e.p.PluginsService] [node-1] loaded module [vectors] [2019-09-12T15:23:22,045][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-ccr] [2019-09-12T15:23:22,046][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-core] [2019-09-12T15:23:22,046][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-deprecation] [2019-09-12T15:23:22,047][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-graph] [2019-09-12T15:23:22,047][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-ilm] [2019-09-12T15:23:22,048][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-logstash] [2019-09-12T15:23:22,048][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-ml] [2019-09-12T15:23:22,048][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-monitoring] [2019-09-12T15:23:22,049][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-rollup] [2019-09-12T15:23:22,050][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-security] [2019-09-12T15:23:22,050][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-sql] [2019-09-12T15:23:22,051][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-voting-only-node] [2019-09-12T15:23:22,051][INFO][o.e.p.PluginsService] [node-1] loaded module [x-pack-watcher] [2019-09-12T15:23:22,052][INFO][o.e.p.PluginsService] [node-1] no plugins loaded [2019-09-12T15:23:29,049][INFO][o.e.x.s.a.s.FileRolesStore] [node-1] parsed [0] roles from file [/etc/elasticsearch/roles.yml] [2019-09-12T15:23:30,521][INFO][o.e.x.m.p.l.CppLogMessageHandler] [node-1] [controller/1948] [Main.cc@110] controller (64 bit): Version 7.3.1 (Build 1d93901e09ef43) Copyright (c) 2019 Elasticsearch BV [2019-09-12T15:23:31,488][DEBUG][o.e.a.ActionModule] [node-1] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security [2019-09-12T15:23:32,095][INFO][o.e.d.DiscoveryModule] [node-1] using discovery type [zen] and seed hosts providers [settings] [2019-09-12T15:23:33,449][INFO][o.e.n.Node] [node-1] initialized [2019-09-12T15:23:33,449][INFO][o.e.n.Node] [node-1] starting ... [2019-09-12T15:23:33,732][INFO][o.e.t.TransportService] [node-1] publish\_address {PUBLICIP:9300}, bound\_addresses {[::]:9300} [2019-09-12T15:23:33,742][INFO][o.e.b.BootstrapChecks] [node-1] bound or publishing to a non-loopback address, enforcing bootstrap checks [2019-09-12T15:23:33,802][INFO][o.e.c.c.Coordinator] [node-1] cluster UUID [0WlayW6tTKWt9Wlz2uj-ZA] [2019-09-12T15:23:34,080][INFO][o.e.c.s.MasterService] [node-1] elected-as-master ([1] nodes joined)[{node-1}{8Jc2DfhjRg2au-tgRu7HMQ}{gnjUgge\_So6\_w23tYrkOdw}{PUBLICIP}{PUBLICIP:9300}{dim}{ml.machine\_memory=3954171904, xpack.installed=true, ml.max\_open\_jobs=20} elect leader, _BECOME\_MASTER\_TASK_, _FINISH\_ELECTION_], term: 56, version: 121, reason: master node changed {previous , current [{node-1}{8Jc2DfhjRg2au-tgRu7HMQ}{gnjUgge\_So6\_w23tYrkOdw}{PUBLICIP}{PUBLICIP:9300}{dim}{ml.machine\_memory=3954171904, xpack.installed=true, ml.max\_open\_jobs=20}]} [2019-09-12T15:23:34,221][INFO][o.e.c.s.ClusterApplierService] [node-1] master node changed {previous , current [{node-1}{8Jc2DfhjRg2au-tgRu7HMQ}{gnjUgge\_So6\_w23tYrkOdw}{PUBLICIP}{PUBLICIP:9300}{dim}{ml.machine\_memory=3954171904, xpack.installed=true, ml.max\_open\_jobs=20}]}, term: 56, version: 121, reason: Publication{term=56, version=121} [2019-09-12T15:23:34,297][INFO][o.e.h.AbstractHttpServerTransport] [node-1] publish\_address {PUBLICIP:9200}, bound\_addresses {[::]:9200} [2019-09-12T15:23:34,298][INFO][o.e.n.Node] [node-1] started [2019-09-12T15:23:34,697][INFO][o.e.l.LicenseService] [node-1] license [bd74b3a7-c8ee-40a4-b84c-c06711b530fd] mode [basic] - valid [2019-09-12T15:23:34,698][INFO][o.e.x.s.s.SecurityStatusChangeListener] [node-1] Active license is now [BASIC]; Security is disabled [2019-09-12T15:23:34,716][INFO][o.e.g.GatewayService] [node-1] recovered [0] indices into cluster\_state ---
**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:** [September 12, 2019, 2:44pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/2 "2019-09-12T14:44:50Z")
Everything looks good here - Elasticsearch has started up normally. In particular the message in the title of your post, "Bound or publishing to a non-loopback address, enforcing bootstrap checks", doesn't indicate any issue. ---
**Author:** ![Ersoy\_Vatansever](https://avatars.discourse-cdn.com/v4/letter/e/51bf81/32.png) [@Ersoy\_Vatansever](https://discuss.elastic.co/u/Ersoy_Vatansever)\ **Post date:** [September 12, 2019, 2:47pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/3 "2019-09-12T14:47:54Z")
Thank you for quick answer. I cant see other node when i run \_cat/nodes my config file cluster.name: my-application node.name: node-1 node.master: true node.data: true node.ingest :false path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch bootstrap.memory\_lock: true network.host: 0.0.0.0 discovery.seed\_hosts: ["PUBLICIP-1", "PUBLICIP-2"] cluster.initial\_master\_nodes: ["node-1", "node-2"] ---
**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:** [September 12, 2019, 2:49pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/4 "2019-09-12T14:49:48Z")
> [@Ersoy\_Vatansever](#): > > `[2019-09-12T15:23:33,802][INFO][o.e.c.c.Coordinator] [node-1] cluster UUID [0WlayW6tTKWt9Wlz2uj-ZA]` Does the other node report a different cluster UUID in its log? If so, see [this note in the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-bootstrap-cluster.html#modules-discovery-bootstrap-cluster-joining) for more information, and instructions on how to resolve it. ---
**Author:** ![Ersoy\_Vatansever](https://avatars.discourse-cdn.com/v4/letter/e/51bf81/32.png) [@Ersoy\_Vatansever](https://discuss.elastic.co/u/Ersoy_Vatansever)\ **Post date:** [September 12, 2019, 2:50pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/5 "2019-09-12T14:50:50Z")
yes, they are different. ---
**Author:** ![Ersoy\_Vatansever](https://avatars.discourse-cdn.com/v4/letter/e/51bf81/32.png) [@Ersoy\_Vatansever](https://discuss.elastic.co/u/Ersoy_Vatansever)\ **Post date:** [September 12, 2019, 2:58pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/6 "2019-09-12T14:58:40Z")
I made configuration like below at first but stil get same result ☹ cluster.name: my-application node.name: node-1 node.master: true node.data: true node.ingest :false path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch bootstrap.memory\_lock: true network.host: 0.0.0.0 discovery.seed\_hosts: ["PUBLICIP-1", "PUBLICIP-2"] cluster.initial\_master\_nodes: ["node-1", "node-2"] ---
**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:** [September 12, 2019, 2:59pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/7 "2019-09-12T14:59:14Z")
Yes, you need to read the note in the docs I linked above. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 10, 2019, 3:09pm UTC](https://discuss.elastic.co/t/bound-or-publishing-to-a-non-loopback-address-enforcing-bootstrap-checks/199276/8 "2019-10-10T15:09:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.