# Elasticsearch not accessible after moving from 1.4.4 to 2.0.0

**URL:** <https://discuss.elastic.co/t/elasticsearch-not-accessible-after-moving-from-1-4-4-to-2-0-0/33601>\
**Category:** Elasticsearch\
**Created:** [November 3, 2015, 7:23am UTC](https://discuss.elastic.co/t/elasticsearch-not-accessible-after-moving-from-1-4-4-to-2-0-0/33601 "2015-11-03T07:23:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nithyanand\_Vasudevan](https://avatars.discourse-cdn.com/v4/letter/n/278dde/32.png) [@Nithyanand\_Vasudevan](https://discuss.elastic.co/u/Nithyanand_Vasudevan)\
**Post date:** [November 3, 2015, 7:23am UTC](https://discuss.elastic.co/t/elasticsearch-not-accessible-after-moving-from-1-4-4-to-2-0-0/33601/1 "2015-11-03T07:23:17Z")

</div>

Hi,

I removed elasticsearch 1.4.4. using rpm. (It was installed using rpm package)

`$rpm -e elasticsearch-1.4.4-1.noarch`  
Then installed 2.0.0 using rpm again and started it as below.

`$rpm -ivh elasticsearch-2.0.0.rpm
$sudo chkconfig --add elasticsearch
$sudo service elasticsearch start`  
Logs show no error or exceptions

`[2015-11-03 12:12:47,903][INFO][node] [Atalon] version[2.0.0], pid[4194], build[de54438/2015-10-22T08:09:48Z]
[2015-11-03 12:12:47,916][INFO][node] [Atalon] initializing ...
[2015-11-03 12:12:48,315][INFO][plugins] [Atalon] loaded [], sites []
[2015-11-03 12:12:48,781][INFO][env] [Atalon] using [1] data paths, mounts [[/ (/dev/mapper/vg01-LogVol00)]], net usable_space [37.2gb], net total_space [90.6gb], spins? [possibly], types [ext4]
[2015-11-03 12:12:59,073][INFO][node] [Atalon] initialized
[2015-11-03 12:12:59,073][INFO][node] [Atalon] starting ...
[2015-11-03 12:12:59,474][INFO][transport] [Atalon] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}, {[::1]:9300}
[2015-11-03 12:12:59,567][INFO][discovery] [Atalon] elasticsearch/RNomvPO4TyyGpRdInlKZ7A
[2015-11-03 12:13:02,804][INFO][cluster.service] [Atalon] new_master {Atalon}{RNomvPO4TyyGpRdInlKZ7A}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2015-11-03 12:13:02,931][INFO][gateway] [Atalon] recovered [0] indices into cluster_state
[2015-11-03 12:13:02,952][INFO][http] [Atalon] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}, {[::1]:9200}
[2015-11-03 12:13:02,953][INFO][node] [Atalon] started`  
However, the curl command gives no response from elasticsearch.

`curl -XGET http://localhost:9200`

Network Error

Network Error (dns\_unresolved\_hostname)

Your requested host "localhost" could not be resolved by DNS.

For assistance, contact your network support team.

When used  
`curl -XGET http://127.0.0.1:9200 `  
I get

Redirection  
Redirect

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [November 3, 2015, 9:21am UTC](https://discuss.elastic.co/t/elasticsearch-not-accessible-after-moving-from-1-4-4-to-2-0-0/33601/2 "2015-11-03T09:21:34Z")

</div>

localhost should always resolve to 127.0.0.1 (and the other way around). Make sure you have

```
127.0.0.1 localhost

```

in your /etc/hosts. I have no explanation for the direction. What does it redirect to? What if you follow the redirection?

---

<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:** [July 5, 2017, 11:40pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accessible-after-moving-from-1-4-4-to-2-0-0/33601/3 "2017-07-05T23:40:59Z")

</div>