# Trouble with Instructions in 'getting started' documentation

**URL:** <https://discuss.elastic.co/t/trouble-with-instructions-in-getting-started-documentation/218584>\
**Category:** Elasticsearch\
**Created:** [February 10, 2020, 12:31pm UTC](https://discuss.elastic.co/t/trouble-with-instructions-in-getting-started-documentation/218584 "2020-02-10T12:31:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kumar.saurabh](https://avatars.discourse-cdn.com/v4/letter/k/edb3f5/32.png) [@kumar.saurabh](https://discuss.elastic.co/u/kumar.saurabh)\
**Post date:** [February 10, 2020, 12:31pm UTC](https://discuss.elastic.co/t/trouble-with-instructions-in-getting-started-documentation/218584/1 "2020-02-10T12:31:28Z")

</div>

I installed Elasticsearch 7.5.2 from the Windows MSI and tried to follow the instructions in the getting started page at [https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-install.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-install.html)  
At the point where the instructions ask for two additional instances to be started, i get errors.  
`elasticsearch -E path.data=data2 -E path.logs=log2`  
I get the error  
`org.elasticsearch.bootstrap.StartupException: BindTransportException[Failed to bind to [9300]]; nested: BindException[Address already in use: bind];`

I followed some discussions and tried to add the following to elasticsearch.yml file  
`node.max_local_storage_nodes: 4`  
It did not help.

Note: I used the command  
`elasticsearch -E path.data=data2 -E path.logs=log2`  
instead of  
`elasticsearch.bat -E path.data=data2 -E path.logs=log2`  
as there is no such batch file in my installation folder.

I might have missed something simple. Help would be appreciated.

---

<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:** [February 10, 2020, 12:53pm UTC](https://discuss.elastic.co/t/trouble-with-instructions-in-getting-started-documentation/218584/2 "2020-02-10T12:53:43Z")

</div>

> [@kumar.saurabh](#):
>
> `... BindException[Address already in use ...`

This indicates you already have a running Elasticsearch node. You will need to shut that down to proceed.

---

<div class="post-metadata">

**Author:** ![kumar.saurabh](https://avatars.discourse-cdn.com/v4/letter/k/edb3f5/32.png) [@kumar.saurabh](https://discuss.elastic.co/u/kumar.saurabh)\
**Post date:** [February 11, 2020, 8:36am UTC](https://discuss.elastic.co/t/trouble-with-instructions-in-getting-started-documentation/218584/3 "2020-02-11T08:36:22Z")

</div>

The 'getting started' tutorial says `Start two more instances of Elasticsearch so you can see how a typical multi-node cluster behaves... The additional nodes are assigned unique IDs. Because you’re running all three nodes locally, they automatically join the cluster with the first node.`  
Is it required to have multiple installations if i have to do this from the same machine?

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [February 11, 2020, 9:15am UTC](https://discuss.elastic.co/t/trouble-with-instructions-in-getting-started-documentation/218584/4 "2020-02-11T09:15:15Z")

</div>

> [@kumar.saurabh](#):
>
> Is it required to have multiple installations if i have to do this from the same machine?

If you're running on Windows, you may want to use the [zip distribution](https://www.elastic.co/guide/en/elasticsearch/reference/current/zip-windows.html) to spin up multiple instances on the same machine.

With the MSI, a **single** installation of Elasticsearch is installed system-wide on the machine. Whilst it is possible to then start **multiple** Elasticsearch processes from a single installation, it requires starting from the command line with arguments to override data, log and configuration paths, which is more fiddly than unzipping the zip distribution three times to three separate directories, and starting elasticsearch in each using the elasticsearch.bat script. If you need to play only with a single node, the MSI is a reasonable choice.

---

<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:** [March 10, 2020, 9:24am UTC](https://discuss.elastic.co/t/trouble-with-instructions-in-getting-started-documentation/218584/5 "2020-03-10T09:24:27Z")

</div>

Closed on March 10, 2020, 9:24am UTC

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