# ElasticSearch 5.1.1 on Ubuntu 16.04, fails when started with \`network.host\` set to 0.0.0.0

**URL:** <https://discuss.elastic.co/t/elasticsearch-5-1-1-on-ubuntu-16-04-fails-when-started-with-network-host-set-to-0-0-0-0/70558>\
**Category:** Elasticsearch\
**Created:** [January 4, 2017, 1:22pm UTC](https://discuss.elastic.co/t/elasticsearch-5-1-1-on-ubuntu-16-04-fails-when-started-with-network-host-set-to-0-0-0-0/70558 "2017-01-04T13:22:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![tomekit](https://avatars.discourse-cdn.com/v4/letter/t/e5b9ba/32.png) [@tomekit](https://discuss.elastic.co/u/tomekit)\
**Post date:** [January 10, 2017, 12:37pm UTC](https://discuss.elastic.co/t/elasticsearch-5-1-1-on-ubuntu-16-04-fails-when-started-with-network-host-set-to-0-0-0-0/70558/5 "2017-01-10T12:37:00Z")

</div>

@junior_h Thanks, I've set these to 1G, as this is my expected heap size. Problem hasn't gone.  
I came across this post: [Memory confusion in Ubuntu 16.04](https://discuss.elastic.co/t/memory-confusion-in-ubuntu-16-04/50961/2)  
and realized that I don't need to lock the memory as I don't have swap on my node anyway.  
Not sure if this might be reason for the `memory_lock` setting to not work, as it clearly says it's a `RLIMIT_MEMLOCK` issue.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-5-1-1-on-ubuntu-16-04-fails-when-started-with-network-host-set-to-0-0-0-0/70558)._