# Network.host issue: elasticsearch.service: Main process exited, code=exited, status=78

**URL:** <https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193>\
**Category:** Elasticsearch\
**Created:** [September 19, 2019, 11:25am UTC](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193 "2019-09-19T11:25:12Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![the1bit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the1bit/32/54500_2.png) [@the1bit](https://discuss.elastic.co/u/the1bit)\
**Post date:** [September 26, 2019, 2:19pm UTC](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193/21 "2019-09-26T14:19:18Z")

</div>

You can find both log here:

- [my-search-failed.log](https://the1bithusacommon.blob.core.windows.net/public/my-search-failed.log)
- [my-search-success.log](https://the1bithusacommon.blob.core.windows.net/public/my-search-success.log)

Nevertheless I am sure - to correct myself - the key here that fact if you would like to configure static (non-localhost) related settings at **network.host** you have to add one of them from **discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes**.

I look forward to hearing from you.

---

<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 26, 2019, 2:28pm UTC](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193/22 "2019-09-26T14:28:47Z")

</div>

> [@the1bit](#):
>
> Nevertheless I am sure - to correct myself - the key here that fact if you would like to configure static (non-localhost) related settings at **network.host** you have to add one of them from **discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes**.

Yes, this is by design, and documented. The fix is simply to set one of these settings (e.g. `discovery.seed_hosts: []`). That's quite different from setting `transport.host: _site_`, which I think has no effect on whether that bootstrap check passes or not.

---

<div class="post-metadata">

**Author:** ![the1bit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the1bit/32/54500_2.png) [@the1bit](https://discuss.elastic.co/u/the1bit)\
**Post date:** [September 26, 2019, 2:30pm UTC](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193/23 "2019-09-26T14:30:45Z")

</div>

> [@DavidTurner](#):
>
> which I think has no effect on whether that bootstrap check passes or not.

You are right. 😉

Thank you for your support.

---

<div class="post-metadata">

**Author:** ![the1bit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the1bit/32/54500_2.png) [@the1bit](https://discuss.elastic.co/u/the1bit)\
**Post date:** [September 26, 2019, 2:31pm UTC](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193/24 "2019-09-26T14:31:34Z")

</div>

Solution: if you would like to configure static (non-localhost) related settings at **network.host** you have to add one of them from **discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes**.

---

<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 24, 2019, 2:31pm UTC](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193/25 "2019-10-24T14:31:43Z")

</div>

Closed on October 24, 2019, 2:31pm UTC

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

[Previous page](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193.md?page=1)
