# Config Elasticsearch for a headless system

**URL:** <https://discuss.elastic.co/t/config-elasticsearch-for-a-headless-system/242312>\
**Category:** Elasticsearch\
**Created:** [July 23, 2020, 9:35am UTC](https://discuss.elastic.co/t/config-elasticsearch-for-a-headless-system/242312 "2020-07-23T09:35:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peter\_Boos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_boos/32/72670_2.png) [@Peter\_Boos](https://discuss.elastic.co/u/Peter_Boos)\
**Post date:** [July 23, 2020, 9:35am UTC](https://discuss.elastic.co/t/config-elasticsearch-for-a-headless-system/242312/1 "2020-07-23T09:35:45Z")

</div>

I'm (trying) to run ELK on a headless console only system.  
So far it only says: **Kibana server is not ready yet**

through a ssh i can see the **tail -f /var/log/syslog**  
Logging this error which is a bit long oneliner :

`Jul 23 11:28:40 ELK kibana[572]: {"type":"log","@timestamp":"2020-07-23T09:28:40Z","tags":["warning","plugins","licensing"],"pid":572,"message":"License information could not be obtained from Elasticsearch due to Not Found :: {\"path\":\"/_xpack\",\"statusCode\":404,\"response\":\"<!DOCTYPE HTML PUBLIC \\\"-//IETF//DTD HTML 2.0//EN\\\">\\n<html><head>\\n<title>404 Not Found</title>\\n</head><body>\\n<h1>Not Found</h1>\\n<p>The requested URL was not found on this server.</p>\\n<hr>\\n<address>Apache/2.4.38 (Debian) Server at 172.16.10.46 Port 80</address>\\n</body></html>\\n\"} error"}`

my etc/kibana/kibana.yml is shown below:

```auto
server.port: 5601
# elasticsearch.url: "http://localhost:92000" // .url didnt workout either
elasticsearch.hosts: http://172.16.10.46
server.host: 172.16.10.46

```

My elasticsearch network settings ( etc/elasticsearch/elasticsearch.yml ) is shown below:

```auto
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
# network.host: 192.168.0.1
# _local_ equals 127.0.0.1 and 0.0.0.0 or a sinigle 0 stands for bind to all IP addresses
# 
network.host: 0
#
# Set a custom port for HTTP:
#
http.port: 9200

```

I'm not sure what goes wrong here, i installed the free versions of all, the errors are about licensing?? but it might as well be i think that one of my above yml files has a wrong settings as i had no clear idea of how that should look like, and i based it eventually on some article i found without knowing if they're ok.

---

<div class="post-metadata">

**Author:** ![Peter\_Boos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_boos/32/72670_2.png) [@Peter\_Boos](https://discuss.elastic.co/u/Peter_Boos)\
**Post date:** [July 23, 2020, 10:05am UTC](https://discuss.elastic.co/t/config-elasticsearch-for-a-headless-system/242312/2 "2020-07-23T10:05:31Z")

</div>

Update :  
I changed a line /etc/kibana/kibana.ym in to

```auto
elasticsearch.hosts : ["http://172.16.10.46:9200"] 

```

It got me rid of the long licensing error, but i got two repeating errors back now:

```auto
Jul 23 12:03:01 ELK kibana[569]: {"type":"log","@timestamp":"2020-07-23T10:03:01Z","tags":["warning","elasticsearch","admin"],"pid":569,"message":"Unable to revive connection: http://172.16.10.46:9200/"}
Jul 23 12:03:01 ELK kibana[569]: {"type":"log","@timestamp":"2020-07-23T10:03:01Z","tags":["warning","elasticsearch","admin"],"pid":569,"message":"No living connections"}

```

I hope someone might recognize what goes wrong here, to me its all new.

---

<div class="post-metadata">

**Author:** ![Peter\_Boos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_boos/32/72670_2.png) [@Peter\_Boos](https://discuss.elastic.co/u/Peter_Boos)\
**Post date:** [July 23, 2020, 10:24am UTC](https://discuss.elastic.co/t/config-elasticsearch-for-a-headless-system/242312/3 "2020-07-23T10:24:18Z")

</div>

Well I think I solved it. Adding a bit more to the previous one.  
Though as a newbie i'm not sure if this is the proper way

Since i was running headless, i couldn't work with local 127.0.0.1

Therefore since its not on 127.0.0.1 it seams to require a change in elasticsearch.yml as well.

Apparently elasticsearch can work over multiple nodes when its in 'production' while **production is every ip not on 127.0.0.1** well i'm headless so i'm in production mode as far as elastic search understands

In production however, elastic search can be configured over multiple servers, and even clusters. And when it startsup it suspects that, so to circumvent that, I needed to tell its only a single server.  
So I altered a line to explain there are no other elastic searchers empty brackets line []

```auto
discovery.seed_hosts: []

```

If this really is the proper answer please someone more experienced confirm then i mark it as solution so others running headless can use it as well

---

<div class="post-metadata">

**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\
**Post date:** [July 23, 2020, 12:36pm UTC](https://discuss.elastic.co/t/config-elasticsearch-for-a-headless-system/242312/4 "2020-07-23T12:36:26Z")

</div>

> [@Peter\_Boos](#):
>
> In production however, Elasticsearch kan be configured over multiple servers, and even clusters.  
> And when it startsup it suspects that, so to circumvent that its only a single server  
> I altered a line to explain there are no other elastic searchers empty brackets line

Hi, Peter. I'm moving this subject to Elasticsearch topic so that someone from the elasticsearch team might confirm this.

---

<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:** [August 20, 2020, 12:36pm UTC](https://discuss.elastic.co/t/config-elasticsearch-for-a-headless-system/242312/5 "2020-08-20T12:36:52Z")

</div>

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