# ES 2.0 deb installation issues **URL:** \ **Category:** Elasticsearch\ **Created:** [November 15, 2015, 12:47am UTC](https://discuss.elastic.co/t/es-2-0-deb-installation-issues/34604 "2015-11-15T00:47:52Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [November 15, 2015, 12:47am UTC](https://discuss.elastic.co/t/es-2-0-deb-installation-issues/34604/1 "2015-11-15T00:47:52Z")
Heya, I'm using the following command to install ES 2.0 on Ubuntu LTS 14.04: `es_version=2.0.0 && curl -s "https://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/distribution/deb/elasticsearch/$es_version/elasticsearch-$es_version.deb" -o elasticsearch-$es_version.deb && sudo dpkg -i elasticsearch-$es_version.deb && sudo update-rc.d elasticsearch defaults 95 10` This used to work before (pre-2.0) but isn't working now. It complains about /usr/share/elasticsearch/config and /usr/share/elasticsearch/log not accessible (which they indeed aren't). I had to manually symlink the /etc and /var paths to the ones ES was expecting: ```auto ln -s /etc/elasticsearch/ /usr/share/elasticsearch/config ln -s /var/log/elasticsearch/ /usr/share/elasticsearch/logs ``` In addition, I can't seem to disable swappiness via `bootstrap.mlockall: true` - ES will complain even when that is set and even when I edit /etc/security/limits.conf manually and restart the service. I'm not quite sure what's going on. I know there have been similar issues with paths in the past, has anything changed in 2.0 that could cause this? Thanks ---
**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:** [November 16, 2015, 3:33am UTC](https://discuss.elastic.co/t/es-2-0-deb-installation-issues/34604/2 "2015-11-16T03:33:21Z")
> [@Itamar\_Syn\_Hershko](#): > > ln -s /etc/elasticsearch/ /usr/share/elasticsearch/config > ln -s /var/log/elasticsearch/ /usr/share/elasticsearch/logs These have never been the default paths, so not sure why it wants them? ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [November 19, 2015, 8:15pm UTC](https://discuss.elastic.co/t/es-2-0-deb-installation-issues/34604/3 "2015-11-19T20:15:54Z")
I wouldn't know... this happens for me on every Ubuntu machine I launch on Azure. Can you check this on your end? have you had reports for similar issues? ---
**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:** [November 20, 2015, 6:07am UTC](https://discuss.elastic.co/t/es-2-0-deb-installation-issues/34604/4 "2015-11-20T06:07:27Z")
I just tried this on an Ubuntu 14.04 machine, didn't run into this! ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [December 5, 2015, 11:00pm UTC](https://discuss.elastic.co/t/es-2-0-deb-installation-issues/34604/5 "2015-12-05T23:00:41Z")
Seems to work fine now - but was happening repeatedly on Azure Ubuntu boxes.. weird.. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:33pm UTC](https://discuss.elastic.co/t/es-2-0-deb-installation-issues/34604/6 "2017-07-05T23:33:20Z")