# Error while installing Elasticsearch in Ubuntu 16.04

**URL:** <https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932>\
**Category:** Elasticsearch\
**Created:** [May 24, 2017, 9:14am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932 "2017-05-24T09:14:56Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johnme](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@Johnme](https://discuss.elastic.co/u/Johnme)\
**Post date:** [May 24, 2017, 9:14am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932/1 "2017-05-24T09:14:56Z")

</div>

I got following error while installing Elasticsearch 5.4.0 from .deb file:

# dpkg -i elasticsearch-5.4.0.deb

Selecting previously unselected package elasticsearch.  
(Reading database ... 54562 files and directories currently installed.)  
Preparing to unpack elasticsearch-5.4.0.deb ...  
Unpacking elasticsearch (5.4.0) ...  
Setting up elasticsearch (5.4.0) ...  
Couldn't write '262144' to 'vm/max\_map\_count', ignoring: Permission denied  
Couldn't write '1' to 'kernel/yama/ptrace\_scope', ignoring: No such file or directory  
Couldn't write '1' to 'kernel/kptr\_restrict', ignoring: Permission denied  
Couldn't write '1' to 'fs/protected\_hardlinks', ignoring: No such file or directory  
Couldn't write '176' to 'kernel/sysrq', ignoring: Permission denied  
Couldn't write '1' to 'fs/protected\_symlinks', ignoring: No such file or directory  
dpkg: error processing package elasticsearch (--install):  
subprocess installed post-installation script returned error exit status 1  
Processing triggers for systemd (229-4ubuntu17) ...  
Errors were encountered while processing:  
elasticsearch

Is this related with vm?

---

<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:** [May 24, 2017, 9:20am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932/2 "2017-05-24T09:20:27Z")

</div>

Are you running that command as root?

---

<div class="post-metadata">

**Author:** ![Johnme](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@Johnme](https://discuss.elastic.co/u/Johnme)\
**Post date:** [May 24, 2017, 9:48am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932/3 "2017-05-24T09:48:42Z")

</div>

yes. by reading documentation we can skip it by setting environment variable

export ES\_SKIP\_SET\_KERNEL\_PARAMETERS=true

But I am not able to start elasticsearch now. It says

# /etc/init.d/elasticsearch status

● elasticsearch.service - Elasticsearch  
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)  
Active: failed (Result: signal) since Wed 2017-05-24 05:52:41 EDT; 1min 46s ago  
Docs: [http://www.elastic.co](http://www.elastic.co)  
Process: 14790 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG\_DIR} -Edefault.path.data=${DATA\_DIR} -Edefault.path.conf=${CONF\_DIR} (code=killed, signal=KILL)  
Process: 14787 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)  
Main PID: 14790 (code=killed, signal=KILL)

May 24 05:52:37 kibana systemd[1]: Starting Elasticsearch...  
May 24 05:52:37 kibana systemd[1]: Started Elasticsearch.  
May 24 05:52:41 kibana systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL  
May 24 05:52:41 kibana systemd[1]: elasticsearch.service: Unit entered failed state.  
May 24 05:52:41 kibana systemd[1]: elasticsearch.service: Failed with result 'signal'.

---

<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:** [May 24, 2017, 9:49am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932/4 "2017-05-24T09:49:39Z")

</div>

Check the ES logs instead.

---

<div class="post-metadata">

**Author:** ![Johnme](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@Johnme](https://discuss.elastic.co/u/Johnme)\
**Post date:** [May 24, 2017, 9:54am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932/5 "2017-05-24T09:54:19Z")

</div>

elasticsearch log is empty ☹

---

<div class="post-metadata">

**Author:** ![Johnme](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@Johnme](https://discuss.elastic.co/u/Johnme)\
**Post date:** [May 25, 2017, 5:50am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932/6 "2017-05-25T05:50:54Z")

</div>

After increasing RAM to 4G I now see logs. It says:

bootstrap checks failed  
max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144]  
system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk

I have inserted following to elasticsearch.yml

bootstrap.system\_call\_filter: false

but not working. After this I changed network.host to localhost instead of public ip, then it worked. But the actual problem is related with OpenVZ and vm.max\_map\_count size. This discussion is all over the github and didnt find any solution which worked.

---

<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:** [June 22, 2017, 5:51am UTC](https://discuss.elastic.co/t/error-while-installing-elasticsearch-in-ubuntu-16-04/86932/7 "2017-06-22T05:51:34Z")

</div>

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