# Problems connecting with other nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [April 4, 2013, 12:49am UTC](https://discuss.elastic.co/t/problems-connecting-with-other-nodes/11439 "2013-04-04T00:49:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![VegHead](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/veghead/32/2411_2.png) [@VegHead](https://discuss.elastic.co/u/VegHead)\ **Post date:** [April 4, 2013, 12:49am UTC](https://discuss.elastic.co/t/problems-connecting-with-other-nodes/11439/1 "2013-04-04T00:49:18Z")
I'm stumped. I'm sure I've got something misconfigured, but I can't figure it out. I am trying to setup a new cluster of two nodes running 0.20.6 on EC2. The EC2 Discovery phase works in that it finds the other potential nodes in the cluster. BUT, the two nodes won't talk to each other. Basically, ES fails to connect to the other node(s) on port 9300: [2013-03-29 11:04:16,642][WARN][discovery.zen.ping.unicast] [ [es3.logstash.ec2.example.com](http://es3.logstash.ec2.example.com)] failed to send ping to [[#cloud-i-12345678-0][inet[/a.b.c.d:9300]]] org.elasticsearch.transport.ReceiveTimeoutTransportException: [][inet[/a.b.c.d:9300]][discovery/zen/unicast] request\_id [4] timed out after [3750ms] As far as I can tell, the problem is that the nodes are not binding to port 9300. Instead they're binding to 9302: 2013-03-29 11:04:09,250][INFO][transport] [ [es3.logstash.ec2.example.com](http://es3.logstash.ec2.example.com)] bound\_address {inet[/0.0.0.0:9302]}, publish\_address {inet[/aa.bb.cc.dd:9302]} If have verified that the security group allows traffic on the port range 9200-9400. If I try to telnet from one of the two nodes to the other on port 9300, telnet hangs. If I try to telnet to port 9302, it works. I also tried disabling EC2 discovery and explicitly listing the nodes using port 9302 (instead of the default 9300) and that worked great: discovery.zen.ping.unicast.hosts: ["[es3.logstash.ec2.example.com:9302](http://es3.logstash.ec2.example.com:9302)"," [es4.logstash.ec2.example.com:9302](http://es4.logstash.ec2.example.com:9302)"] If I try explicitly forcing the transport port to 9300 and the http port to 9200, ElasticSearch complains that the ports are already in use and shuts back down. If I use unicast, set the host names directly in the config and specify port 9302, it works fine and the two nodes talk to each other. My discovery configuration looks like the following: discovery.type: ec2 discovery.zen.minimum\_master\_nodes: 1 discovery.zen.ping.multicast.enabled: false cloud.node.auto\_attributes: true cloud.aws.region: us-east-1 discovery.ec2.groups: ElasticSearchLogstash Any bright ideas? I'm pretty much dead in the water until I can get this working... -Sean -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [April 4, 2013, 7:01am UTC](https://discuss.elastic.co/t/problems-connecting-with-other-nodes/11439/2 "2013-04-04T07:01:31Z")
Hey, this looks like there is already another service running on port 9300 and 9200. If you are on linux you can verify this with 'lsof' or 'netstat -tulpe' (as root). Maybe you started an elasticsearch instance already with different configurations some time ago. On Thu, Apr 4, 2013 at 2:49 AM, VegHead [organicveggie@gmail.com](mailto:organicveggie@gmail.com) wrote: > I'm stumped. I'm sure I've got something misconfigured, but I can't figure > it out. > > I am trying to setup a new cluster of two nodes running 0.20.6 on EC2. The > EC2 Discovery phase works in that it finds the other potential nodes in the > cluster. BUT, the two nodes won't talk to each other. Basically, ES fails > to connect to the other node(s) on port 9300: > > [2013-03-29 11:04:16,642][WARN][discovery.zen.ping.unicast] [ > [es3.logstash.ec2.example.com](http://es3.logstash.ec2.example.com)] failed to send ping to > [[#cloud-i-12345678-0][inet[/\*\*a.b.c.d:9300]]] > org.elasticsearch.transport. **ReceiveTimeoutTransportExcepti** on: > [inet[/a.b.c.d:9300]][\*\*discovery/zen/unicast] request\_id [4] timed out > after [3750ms] > > As far as I can tell, the problem is that the nodes are not binding to > port 9300. Instead they're binding to 9302: > > 2013-03-29 11:04:09,250][INFO][transport] [ > [es3.logstash.ec2.example.com](http://es3.logstash.ec2.example.com)] bound\_address {inet[/0.0.0.0:9302]}, > publish\_address {inet[/aa.bb.cc.dd:9302]} > > If have verified that the security group allows traffic on the port range > 9200-9400. If I try to telnet from one of the two nodes to the other on > port 9300, telnet hangs. If I try to telnet to port 9302, it works. I also > tried disabling EC2 discovery and explicitly listing the nodes using port > 9302 (instead of the default 9300) and that worked great: > > discovery.zen.ping.unicast.\*\*hosts: ["es3.logstash.ec2.example.\*\*com:9302[http://es3.logstash.ec2.example.com:9302/](http://es3.logstash.ec2.example.com:9302/) > ","es4.logstash.ec2.\*\*[example.com:9302](http://example.com:9302)[http://es4.logstash.ec2.example.com:9302/](http://es4.logstash.ec2.example.com:9302/) > "] > > If I try explicitly forcing the transport port to 9300 and the http port > to 9200, Elasticsearch complains that the ports are already in use and > shuts back down. > > If I use unicast, set the host names directly in the config and specify > port 9302, it works fine and the two nodes talk to each other. > > My discovery configuration looks like the following: > > discovery.type: ec2 > discovery.zen.minimum\_master\_\*\*nodes: 1 > discovery.zen.ping.multicast.\*\*enabled: false > cloud.node.auto\_attributes: true > cloud.aws.region: us-east-1 > discovery.ec2.groups: ElasticSearchLogstash > > Any bright ideas? I'm pretty much dead in the water until I can get this > working... > > -Sean > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:42am UTC](https://discuss.elastic.co/t/problems-connecting-with-other-nodes/11439/3 "2017-07-06T02:42:51Z")