# Nodes say "connection refused" after updating to Debian 8.6 on AWS

**URL:** <https://discuss.elastic.co/t/nodes-say-connection-refused-after-updating-to-debian-8-6-on-aws/63072>\
**Category:** Elasticsearch\
**Created:** [October 14, 2016, 6:12pm UTC](https://discuss.elastic.co/t/nodes-say-connection-refused-after-updating-to-debian-8-6-on-aws/63072 "2016-10-14T18:12:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jared\_Miller](https://avatars.discourse-cdn.com/v4/letter/j/3be4f8/32.png) [@Jared\_Miller](https://discuss.elastic.co/u/Jared_Miller)\
**Post date:** [October 14, 2016, 6:12pm UTC](https://discuss.elastic.co/t/nodes-say-connection-refused-after-updating-to-debian-8-6-on-aws/63072/1 "2016-10-14T18:12:42Z")

</div>

I manage my clusters (v2.4) on AWS using CloudFormation. I have dedicated data nodes, a dedicated master, and a load balancer in front of the data nodes for the convenience of having one URL to reach the cluster.

Recently I updated from Debian 8.4 AMIs to 8.6 AMIs, and suddenly the clusters stopped coming up properly. There are no errors in the logs, and the nodes seem to be discovering each other and the master node, but the load balancer can no longer register the data nodes as being healthy (using [http://node-internal-dns:9200/\_cluster/health](http://node-internal-dns:9200/_cluster/health)), and trying to hit the data nodes with curl on port 9200 yields an immediate "Connection refused". My security groups, networking, etc. didn't change ... only the switch to Debian 8.6 AMI.

My data node configuration looks like this:

```
cluster.name: XXX
node.master: false
plugin.mandatory: cloud-aws
http.host: _ec2:privateDns_
network.host: _ec2:privateIpv4_
discovery.type: ec2
discovery.zen.ping.multicast.enabled: false
discovery.zen.minimum_master_nodes: 1
cloud.aws.region: us-west-2
cloud.aws.groups: sg-XXX

```

How can I go about debugging this problem?

---

<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:** [October 15, 2016, 8:59pm UTC](https://discuss.elastic.co/t/nodes-say-connection-refused-after-updating-to-debian-8-6-on-aws/63072/2 "2016-10-15T20:59:04Z")

</div>

What do the ES logs show? Is there a firewall that may have autostarted after the upgrade?

> [@Jared\_Miller](#):
>
> discovery.zen.minimum\_master\_nodes: 1

That's not ideal, see [Important Configuration Changes | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/2.x/important-configuration-changes.html#_minimum_master_nodes)

---

<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, 10:11pm UTC](https://discuss.elastic.co/t/nodes-say-connection-refused-after-updating-to-debian-8-6-on-aws/63072/3 "2017-07-05T22:11:59Z")

</div>

Closed on July 5, 2017, 10:11pm UTC