# \[Resolved\]\[ES7.0.1\] Exception \[o.e.d.SeedHostsResolver \] \[node-1\] failed to resolve host \[node-1\] when starting es

**URL:** <https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960>\
**Category:** Elasticsearch\
**Created:** [September 4, 2019, 12:53am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960 "2019-09-04T00:53:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cheriemilk](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@cheriemilk](https://discuss.elastic.co/u/cheriemilk)\
**Post date:** [September 4, 2019, 12:53am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/1 "2019-09-04T00:53:23Z")

</div>

Hi team,

I got below error when starting es7.0.1, how to correct the yml configuration file to resolve it?

> ```
> [2019-09-04T08:40:22,339][INFO][o.e.h.AbstractHttpServerTransport] [node-1] publish_address {10.59.181.210:9200}, bound_addresses {[::]:9200}
> [2019-09-04T08:40:22,343][INFO][o.e.n.Node] [node-1] started
> [2019-09-04T08:40:23,890][WARN][o.e.d.SeedHostsResolver] [node-1] failed to resolve host [node-1]
> java.net.UnknownHostException: node-1
> at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[?:1.8.0_144]
> at java.net.InetAddress$3.lookupAllHostAddr(InetAddress.java:971) ~[?:1.8.0_144]
> at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1366) ~[?:1.8.0_144]
> at java.net.InetAddress.getAllByName0(InetAddress.java:1319) ~[?:1.8.0_144]
> at java.net.InetAddress.getAllByName(InetAddress.java:1235) ~[?:1.8.0_144]
> at java.net.InetAddress.getAllByName(InetAddress.java:1169) ~[?:1.8.0_144]
> at org.elasticsearch.transport.TcpTransport.parse(TcpTransport.java:536) ~[elasticsearch-7.0.1.jar:7.0.1]
> at org.elasticsearch.transport.TcpTransport.addressesFromString(TcpTransport.java:489) ~[elasticsearch-7.0.1.jar:7.0.1]
> at org.elasticsearch.transport.TransportService.addressesFromString(TransportService.java:744) ~[elasticsearch-7.0.1.jar:7.0.1]
> at org.elasticsearch.discovery.SeedHostsResolver.lambda$resolveHostsLists$0(SeedHostsResolver.java:143) ~[elasticsearch-7.0.1.jar:7.0.1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_144]
> at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) ~[elasticsearch-7.0.1.jar:7.0.1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_144]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_144]
> at java.lang.Thread.run(Thread.java:808) [?:1.8.0_144]
> 
> ```

Thanks,  
Cherie

---

<div class="post-metadata">

**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 4, 2019, 9:02am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/2 "2019-09-04T09:02:27Z")

</div>

You have `node-1` defined as the address of a seed host (e.g. in `discovery.seed_hosts`) but this does not resolve to an IP address that Elasticsearch can use. Either delete this entry from your seed hosts, or else fix your DNS so that this entry _does_ resolve to an IP address.

---

<div class="post-metadata">

**Author:** ![cheriemilk](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@cheriemilk](https://discuss.elastic.co/u/cheriemilk)\
**Post date:** [September 5, 2019, 7:30am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/3 "2019-09-05T07:30:54Z")

</div>

Hi David,

You mean either I

1. Specify the IP in discovery.seed\_hosts  
OR
2. comment discovery.seed\_hosts: ["node-1"] from elasticsearch.yml?

Thanks,  
Cherie

Thanks,  
Cherie

---

<div class="post-metadata">

**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 5, 2019, 8:12am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/4 "2019-09-05T08:12:58Z")

</div>

1. Yes, the IP address should avoid this, as would a name that DNS knows about that resolves to that IP address.

2. Possibly, although I can think of some reasons why that might not work. You could also try setting it to an empty list: `discovery.seed_hosts: []`.

---

<div class="post-metadata">

**Author:** ![cheriemilk](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@cheriemilk](https://discuss.elastic.co/u/cheriemilk)\
**Post date:** [September 5, 2019, 8:49am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/5 "2019-09-05T08:49:24Z")

</div>

I enabled 2 configurations in yml file: discovery.seed\_hosts AND discovery.zen.ping.unicast.hosts.

when starting elasticsearch, it says

`

> it is forbidden to set both [discovery.seed\_hosts] and [discovery.zen.ping.unicast.hosts]

`

1. which one of these 2 is mandatory when starting elasticsearch?
2. what is the lowest level configuration to start elasticsearch?

Thanks,  
Cherie

---

<div class="post-metadata">

**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 5, 2019, 8:51am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/6 "2019-09-05T08:51:19Z")

</div>

You shouldn't be setting `discovery.zen.ping.unicast.hosts`. This setting is renamed to `discovery.seed_hosts` and the old name is deprecated.

---

<div class="post-metadata">

**Author:** ![cheriemilk](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@cheriemilk](https://discuss.elastic.co/u/cheriemilk)\
**Post date:** [September 5, 2019, 8:51am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/7 "2019-09-05T08:51:56Z")

</div>

Oh.. OK. thanks

---

<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:** [October 3, 2019, 8:51am UTC](https://discuss.elastic.co/t/resolved-es7-0-1-exception-o-e-d-seedhostsresolver-node-1-failed-to-resolve-host-node-1-when-starting-es/197960/8 "2019-10-03T08:51:56Z")

</div>

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