# Zen errror in ec2

**URL:** <https://discuss.elastic.co/t/zen-errror-in-ec2/5899>\
**Category:** Elasticsearch\
**Created:** [November 17, 2011, 2:40pm UTC](https://discuss.elastic.co/t/zen-errror-in-ec2/5899 "2011-11-17T14:40:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![achaayan](https://avatars.discourse-cdn.com/v4/letter/a/dbc845/32.png) [@achaayan](https://discuss.elastic.co/u/achaayan)\
**Post date:** [November 17, 2011, 2:40pm UTC](https://discuss.elastic.co/t/zen-errror-in-ec2/5899/1 "2011-11-17T14:40:59Z")

</div>

## Hi, I am trying to set up ES on EC2. I have set up discovery mode as ec2 in the configuration file:

## discovery: type: ec2

## ES seems to be responding fine. However, when I check the console output, I see success message from ec2 discovery and then a failure message from zen:

## [TRACE][_discovery.zen.ping.unicast_] [Amanda Sefton] [1] failed to connect to [#domain][inet[/XX.XXX.XXX.XXX:9300]] org.elasticsearch.transport.ConnectTransportException: [][inet[/XX.XXX.XXX.XXX:9300]] connect\_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:535) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:501) at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:480) at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:128) at org.elasticsearch.discovery.zen.ping.unicast._UnicastZenPing_ $3.run(UnicastZenPing.java:273) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:384) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:354) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:276) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44)

Please let me know what I am doing wrong.

Thanks!!

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [November 20, 2011, 7:58am UTC](https://discuss.elastic.co/t/zen-errror-in-ec2/5899/2 "2011-11-20T07:58:26Z")

</div>

There might be connection failure from one node to the other, if the other  
node has not started yet. If the other node that fails to connect to is up,  
check things like security groups and the like, make sure they can connect  
to each other (the host and port 9300).

On Thu, Nov 17, 2011 at 4:40 PM, achaayan [felixmd@gmail.com](mailto:felixmd@gmail.com) wrote:

> ## Hi, I am trying to set up ES on EC2. I have set up discovery mode as ec2 in the configuration file:
> 
> ## discovery: type: ec2
> 
> ## ES seems to be responding fine. However, when I check the console output, I see success message from ec2 discovery and then a failure message from zen:
> 
> [TRACE][_discovery.zen.ping.unicast_] [Amanda Sefton] [1]  
> failed to connect to [#domain][inet[/XX.XXX.XXX.XXX:9300]]  
> org.elasticsearch.transport.ConnectTransportException:  
> [inet[/XX.XXX.XXX.XXX:9300]] connect\_timeout[30s]  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:535)  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:501)  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:480)  
> at  
> org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:128)  
> at org.elasticsearch.discovery.zen.ping.unicast._UnicastZenPing_  
> $3.run(UnicastZenPing.java:273)  
> at  
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)  
> at java.lang.Thread.run(Thread.java:636)  
> Caused by: java.net.ConnectException: Connection refused  
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)  
> at  
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592)  
> at  
> org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:384)  
> at  
> org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:354)  
> at  
> org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:276)  
> at  
> org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)  
> at  
> org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44)
> 
> * * *
> 
> Please let me know what I am doing wrong.
> 
> Thanks!!

---

<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 6, 2017, 3:48am UTC](https://discuss.elastic.co/t/zen-errror-in-ec2/5899/3 "2017-07-06T03:48:10Z")

</div>


