# Default Install Configuration

**URL:** <https://discuss.elastic.co/t/default-install-configuration/71934>\
**Category:** Elasticsearch\
**Created:** [January 18, 2017, 3:47am UTC](https://discuss.elastic.co/t/default-install-configuration/71934 "2017-01-18T03:47:18Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kopacko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kopacko/32/10733_2.png) [@kopacko](https://discuss.elastic.co/u/kopacko)\
**Post date:** [January 18, 2017, 3:47am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/1 "2017-01-18T03:47:18Z")

</div>

I am in the process of rebuilding my ELK stack instances in all my office locations (28 locations). So tonight, after installing Ubuntu 16.04 on each server and patching, I start the install process for Elasticsearch.

After installing Java, I proceed to install Elasticsearch. Half the installs have one default config file and the other half, have an entirely different default config file. How is this possible? What do I need to do, to make sure my configs are the same?

---

<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:** [January 18, 2017, 3:53am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/2 "2017-01-18T03:53:52Z")

</div>

We recommend the use of config management - Puppet, chef, ansible, salt, whatever.

However unless you purge previous installs, it'll keep config files around. That may be what you are seeing.

---

<div class="post-metadata">

**Author:** ![kopacko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kopacko/32/10733_2.png) [@kopacko](https://discuss.elastic.co/u/kopacko)\
**Post date:** [January 18, 2017, 4:03am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/3 "2017-01-18T04:03:46Z")

</div>

Yea I'm not paying for Puppet or Chef for base installs and some config files.

These were fresh installs. I deleted the disks in vSphere and installed from scratch. But this didnt answer my question, why the different config files?

I'm rebuilding one of my data center clusters which is an 8 server cluster and even those 8 servers have differing config files.

---

<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:** [January 18, 2017, 4:05am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/4 "2017-01-18T04:05:31Z")

</div>

> [@kopacko](#):
>
> Yea I'm not paying for Puppet or Chef for base installs and some config files.

They're open source?

> [@kopacko](#):
>
> I'm rebuilding one of my data center clusters which is an 8 server cluster and even those 8 servers have differing config files.

Can you show us? How are you installing them?

---

<div class="post-metadata">

**Author:** ![kopacko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kopacko/32/10733_2.png) [@kopacko](https://discuss.elastic.co/u/kopacko)\
**Post date:** [January 18, 2017, 4:24am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/5 "2017-01-18T04:24:20Z")

</div>

Open source doesn't mean free. Puppet charges 75 dollars per server for maintenance and support.

Again, I have my Logstash config files all centrally located, so aside from installing Ubuntu and ELK, nothing else gets done on these boxes.

These are my steps, as compiled off the Elasticsearch install guide (hopefully it makes sense):

```auto
	[Install Java]

```

- sudo add-apt-repository -y ppa:webupd8team/java
- sudo apt-get update
- sudo apt-get -y install oracle-java8-installer

```auto
	[Install Elasticsearch]

```

- wget -qO - [https://artifacts.elastic.co/GPG-KEY-elasticsearch](https://artifacts.elastic.co/GPG-KEY-elasticsearch) | sudo apt-key add -
- sudo apt-get install apt-transport-https
- echo "deb [https://artifacts.elastic.co/packages/5.x/apt](https://artifacts.elastic.co/packages/5.x/apt) stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-5.x.list
- sudo apt-get update && sudo apt-get install elasticsearch

```auto
	[ELASTICSEARCH CONFIG]

```

- sudo vi /etc/elasticsearch/elasticsearch.yml

```auto
=> cluster.name: ####ELK

```

=\> [node.name](http://node.name): ${HOSTNAME}

```auto
=> bootstrap.memory_lock: true

```

=\> network.host: localhost

```auto

* sudo vi /etc/default/elasticsearch

```

=\> MAX\_LOCKED\_MEMORY=unlimited

```auto

* sudo vi /etc/elasticsearch/jvm.options

```

=\> -Xms#g  
=\> -Xmx#g

```auto

* sudo vi /usr/lib/sysctl.d/elasticsearch.conf

```

=\> m.max\_map\_count=262144

```auto

* sudo vi /usr/lib/systemd/system/elasticsearch.service

```

=\> LimitNOFILE=131070

```auto
=> LimitMEMLOCK=infinity

```

- sudo vi /etc/security/limits.conf

```auto
=> elasticsearch - nofile 65536
=> elasticsearch - nproc 2048

```

[CLI COMMAND]  
sudo sysctl vm.max\_map\_count=262144

That is my cheat sheet for lack of a better description when it comes to deploying Elasticsearch.

---

<div class="post-metadata">

**Author:** ![kopacko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kopacko/32/10733_2.png) [@kopacko](https://discuss.elastic.co/u/kopacko)\
**Post date:** [January 18, 2017, 4:40am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/6 "2017-01-18T04:40:47Z")

</div>

This is a bit on the ridiculous side...some of these installs are missing the jvm.options file.

---

<div class="post-metadata">

**Author:** ![kopacko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kopacko/32/10733_2.png) [@kopacko](https://discuss.elastic.co/u/kopacko)\
**Post date:** [January 18, 2017, 5:06am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/7 "2017-01-18T05:06:18Z")

</div>

Mark,  
I think I figured out what the deal was. Apparently several servers did NOT accept this command:

> echo "deb [https://artifacts.elastic.co/packages/5.x/apt](https://artifacts.elastic.co/packages/5.x/apt) stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-5.x.list

As a result, some "other" version of Elasticsearch was installed, not 5.1.2.

---

<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:** [February 15, 2017, 5:06am UTC](https://discuss.elastic.co/t/default-install-configuration/71934/8 "2017-02-15T05:06:54Z")

</div>

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