# Running-multiple-instance-of-elk-on-same-machine

**URL:** <https://discuss.elastic.co/t/running-multiple-instance-of-elk-on-same-machine/89165>\
**Category:** Kibana\
**Created:** [June 13, 2017, 9:43am UTC](https://discuss.elastic.co/t/running-multiple-instance-of-elk-on-same-machine/89165 "2017-06-13T09:43:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishalkin](https://avatars.discourse-cdn.com/v4/letter/v/ccd318/32.png) [@vishalkin](https://discuss.elastic.co/u/vishalkin)\
**Post date:** [June 13, 2017, 9:43am UTC](https://discuss.elastic.co/t/running-multiple-instance-of-elk-on-same-machine/89165/1 "2017-06-13T09:43:27Z")

</div>

I have an ELK Stack 5.1.1 running on one machine and at the same time I am installing another instance of ELK (5.2.2) on the same machine running 5.1.1.

I have made following changes to

**elasticsearch.yml**

> http.port: 9222 to http.port: 9222

**kibana.yml**

> server.port: 5661  
> server.host: 0.0.0.0  
> elasticsearch.url: [http://localhost:9222](http://localhost:9222)

When I try to run kibana 5.2.2 (ES 5.2.2 is running on 127.0.0.1:9222)  
I get following error:

```
log [08:58:41.057] [info][status][plugin:kibana@5.2.2] Status changed from uninitialized to green - Ready
  log [08:58:41.171] [info][status][plugin:elasticsearch@5.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log [08:58:41.230] [info][status][plugin:console@5.2.2] Status changed from uninitialized to green - Ready
  log [08:58:41.246] [error][status][plugin:elasticsearch@5.2.2] Status changed from yellow to red - This version of Kibana requires Elasticsearch v5.2.2 on all nodes. I found the following incompatible nodes in your cluster: v5.1.1 @ 127.0.0.1:9200 (127.0.0.1)
  log [08:58:41.487] [info][status][plugin:timelion@5.2.2] Status changed from uninitialized to green - Ready
  log [08:58:41.492] [info][listening] Server running at http://servername.com:5661
  log [08:58:41.494] [error][status][ui settings] Status changed from uninitialized to red - Elasticsearch plugin is red

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 13, 2017, 9:59am UTC](https://discuss.elastic.co/t/running-multiple-instance-of-elk-on-same-machine/89165/2 "2017-06-13T09:59:56Z")

</div>

> [@vishalkin](#):
>
> log [08:58:41.246] [error][status][plugin:elasticsearch@5.2.2] Status changed from yellow to red - This version of Kibana requires Elasticsearch v5.2.2 on all nodes. I found the following incompatible nodes in your cluster: v5.1.1 @ 127.0.0.1:9200 (127.0.0.1)

Looks like it hasn't picked up the config change.

However why not use something like docker to do 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:** [July 11, 2017, 10:00am UTC](https://discuss.elastic.co/t/running-multiple-instance-of-elk-on-same-machine/89165/3 "2017-07-11T10:00:11Z")

</div>

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