# Ip field from \_cat/nodes shows loopback for one host in cluster?

**URL:** <https://discuss.elastic.co/t/ip-field-from--cat-nodes-shows-loopback-for-one-host-in-cluster/24191>\
**Category:** Elasticsearch\
**Created:** [June 23, 2015, 11:50am UTC](https://discuss.elastic.co/t/ip-field-from--cat-nodes-shows-loopback-for-one-host-in-cluster/24191 "2015-06-23T11:50:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JeremyinNC](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeremyinnc/32/44868_2.png) [@JeremyinNC](https://discuss.elastic.co/u/JeremyinNC)\
**Post date:** [June 23, 2015, 11:50am UTC](https://discuss.elastic.co/t/ip-field-from--cat-nodes-shows-loopback-for-one-host-in-cluster/24191/1 "2015-06-23T11:50:54Z")

</div>

\_cat/nodes?v gives me the results below. Can someone tell me why 05 is showing the loopback IP? That is NOT the host I am running curl on, it does this from any box!

```
host ip heap.percent ram.percent load node.role master name
dev-logstash02.aws.company.com 192.168.29.208 85 49 4.89 d * dev-logstash02 
dev-logstash05.aws.company.com 127.0.1.1 63 58 1.47 d - dev-logstash05
dev-logstash03.aws.company.com 192.168.29.45 85 48 0.54 d m dev-logstash03 
dev-logstash04.aws.company.com 192.168.28.75 70 46 1.03 d - dev-logstash04 
dev-logstash01.aws.company.com 192.168.29.152 21 54 1.74 d - dev-logstash01 

```

This is on ES 1.4.5 on AWS linux

---

<div class="post-metadata">

**Author:** ![ottignon](https://avatars.discourse-cdn.com/v4/letter/o/7cd45c/32.png) [@ottignon](https://discuss.elastic.co/u/ottignon)\
**Post date:** [December 18, 2015, 5:52pm UTC](https://discuss.elastic.co/t/ip-field-from--cat-nodes-shows-loopback-for-one-host-in-cluster/24191/2 "2015-12-18T17:52:10Z")

</div>

I have exactly the same problem, using the official elasticsearch puppet module:

```
node opselasticsearch1 {
include default_classes
include limits::elasticsearch
$init_hash = {
        'ES_HEAP_SIZE' => '4g',
        }
class { 'elasticsearch':
        init_defaults => $init_hash,
        datadir => '/elasticsearch_index_store_1',
        config => {
                'cluster.name' => 'operational-monitoring-1',
                'http.port' => '9200',
                'transport.tcp.port' => '9300',
                'network.bind_host' => ['localhost', '10.100.112.210'],
                'network.publish_host' => '10.100.112.210',
                'bootstrap.mlockall' => 'true'
                };
        }
elasticsearch::instance { 'es-01':
        config => { 'node.name' => 'opselasticsearch1-es-01', 'node.master' => 'false' }
        }
}

node opselasticsearch2 {
include default_classes
include limits::elasticsearch
$init_hash = {
        'ES_HEAP_SIZE' => '7g',
        }
class { 'elasticsearch':
        init_defaults => $init_hash,
        datadir => '/elasticsearch_index_store_1',
        config => {
                'cluster.name' => 'operational-monitoring-1',
                'http.port' => '9200',
                'transport.tcp.port' => '9300',
                'network.bind_host' => ['localhost', '10.100.112.211'],
                'network.publish_host' => '10.100.112.211',
                'bootstrap.mlockall' => 'true'
                };
        }
elasticsearch::instance { 'es-01':
        config => { 'node.name' => 'opselasticsearch2-es-01' }
        }
}

node opselasticsearch3 {
include default_classes
include limits::elasticsearch
$init_hash = {
        'ES_HEAP_SIZE' => '15g',
        }
class { 'elasticsearch':
        init_defaults => $init_hash,
        datadir => '/elasticsearch_index_store_1',
        config => {
                'cluster.name' => 'operational-monitoring-1',
                'http.port' => '9200',
                'transport.tcp.port' => '9300',
                'network.bind_host' => ['localhost', '10.100.112.212'],
                'network.publish_host' => '10.100.112.212',
                'bootstrap.mlockall' => 'true'
                };
        }
elasticsearch::instance { 'es-01':
        config => { 'node.name' => 'opselasticsearch3-es-01', 'node.data' => 'false' }
        }
}
```

---

<div class="post-metadata">

**Author:** ![ottignon](https://avatars.discourse-cdn.com/v4/letter/o/7cd45c/32.png) [@ottignon](https://discuss.elastic.co/u/ottignon)\
**Post date:** [December 18, 2015, 6:02pm UTC](https://discuss.elastic.co/t/ip-field-from--cat-nodes-shows-loopback-for-one-host-in-cluster/24191/3 "2015-12-18T18:02:00Z")

</div>

Adding the nodes into /etc/hosts appears to have resolved the issue for me.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:29pm UTC](https://discuss.elastic.co/t/ip-field-from--cat-nodes-shows-loopback-for-one-host-in-cluster/24191/4 "2017-07-05T23:29:54Z")

</div>