# Elasticsearch unavailable during upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [January 13, 2016, 6:34pm UTC](https://discuss.elastic.co/t/elasticsearch-unavailable-during-upgrade/39146 "2016-01-13T18:34:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jzheaux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jzheaux/32/7138_2.png) [@jzheaux](https://discuss.elastic.co/u/jzheaux)\ **Post date:** [January 13, 2016, 6:34pm UTC](https://discuss.elastic.co/t/elasticsearch-unavailable-during-upgrade/39146/1 "2016-01-13T18:34:50Z")
We are in the process of upgrading from 1.6 to 2.1. The logs show a lot of activity with regard to upgrading each index; however, during that time, connections on 9200 are refused. Is that expected behavior? ---
**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 13, 2016, 9:23pm UTC](https://discuss.elastic.co/t/elasticsearch-unavailable-during-upgrade/39146/2 "2016-01-13T21:23:30Z")
What sort of connections? What state is the cluster in? ---
**Author:** ![jzheaux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jzheaux/32/7138_2.png) [@jzheaux](https://discuss.elastic.co/u/jzheaux)\ **Post date:** [January 14, 2016, 9:30pm UTC](https://discuss.elastic.co/t/elasticsearch-unavailable-during-upgrade/39146/3 "2016-01-14T21:30:12Z")
http connections. [https://localhost:9200](https://localhost:9200) returns a connection refused. Typically, there is a message in the logs like "[servername] publish\_address {ipaddress:9200}, bound\_address{[::]:9200}" I don't see this in the logs during the upgrade, so I suppose this is why 9200 isn't responding. It just seems incorrect to not see that message since there is an upgrade-status url that one can ostensibly hit while the system is upgrading. When you ask "what state", I can't query the red/yellow/green state since connections are refused on 9200, or is there another way for me to query that? ---
**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 14, 2016, 9:37pm UTC](https://discuss.elastic.co/t/elasticsearch-unavailable-during-upgrade/39146/4 "2016-01-14T21:37:26Z")
Take a look at [Connectivity issues with a new/upgraded 2.X cluster? Read here first :)](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699) ---
**Author:** ![jzheaux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jzheaux/32/7138_2.png) [@jzheaux](https://discuss.elastic.co/u/jzheaux)\ **Post date:** [January 14, 2016, 9:46pm UTC](https://discuss.elastic.co/t/elasticsearch-unavailable-during-upgrade/39146/5 "2016-01-14T21:46:49Z")
I'm familiar with the document. When there are no indices to upgrade, I am able to hit the cluster just fine because I've already set network.host to 0.0.0.0. It is during the index upgrade that I can't get a response. Thus far, I've tried 0.0.0.0 and _non\_loopback_. I will try some other values for network.host to see what kind of behavior I get. If my ES 2.1 cluster is pointed at a data mount with no indices to upgrade, 9200 responds fine. ---
**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:24pm UTC](https://discuss.elastic.co/t/elasticsearch-unavailable-during-upgrade/39146/6 "2017-07-05T23:24:19Z")