# EC2 discovery is not working for me **URL:** \ **Category:** Elasticsearch\ **Created:** [September 9, 2011, 4:15am UTC](https://discuss.elastic.co/t/ec2-discovery-is-not-working-for-me/5335 "2011-09-09T04:15:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Marty1](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@Marty1](https://discuss.elastic.co/u/Marty1)\ **Post date:** [September 9, 2011, 4:15am UTC](https://discuss.elastic.co/t/ec2-discovery-is-not-working-for-me/5335/1 "2011-09-09T04:15:17Z")
I'm getting the following: [2011-09-08 21:14:17,793][INFO][node] [Pyre] {elasticsearch/0.17.6}[8746]: initializing ... [2011-09-08 21:14:17,808][INFO][plugins] [Pyre] loaded [cloud-aws], sites [] [2011-09-08 21:14:20,633][INFO][node] [Pyre] {elasticsearch/0.17.6}[8746]: initialized [2011-09-08 21:14:20,633][INFO][node] [Pyre] {elasticsearch/0.17.6}[8746]: starting ... [2011-09-08 21:14:20,722][INFO][transport] [Pyre] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ 10.38.111.22:9300]} [2011-09-08 21:14:26,632][WARN][transport.netty] [Pyre] Message not fully read (response) for [6] handler future(org.elasticsearch.discovery.zen.membership.MembershipAction $1@397b6074), error [false], resetting [2011-09-08 21:14:26,632][INFO][discovery.ec2] [Pyre] failed to send join request to master [[Coral][9H4lLBnlQoGTs34jhIPKug] [inet[/10.84.129.100:9300]]], reason [org.elasticsearch.transport.RemoteTransportException: Failed to deserialize response of type [org.elasticsearch.discovery.zen.membership.MembershipAction $JoinResponse]; org.elasticsearch.transport.TransportSerializationException: Failed to deserialize response of type [org.elasticsearch.discovery.zen.membership.MembershipAction $JoinResponse]; java.io.IOException: Expected handle header, got [110]] I verified though the console that I can create keys in the s3 bucket. Any guesses what operation is failing? Thanks! ---
**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\ **Post date:** [September 9, 2011, 9:56am UTC](https://discuss.elastic.co/t/ec2-discovery-is-not-working-for-me/5335/2 "2011-09-09T09:56:03Z")
bound\_address {inet[/0:0:0:0:0:0:0:0:9300]} What's your config? Looks like you're not specifying a host? On Fri, Sep 9, 2011 at 5:15 AM, Marty [marty@pinterest.com](mailto:marty@pinterest.com) wrote: > I'm getting the following: > [2011-09-08 21:14:17,793][INFO][node] [Pyre] > {elasticsearch/0.17.6}[8746]: initializing ... > [2011-09-08 21:14:17,808][INFO][plugins] [Pyre] > loaded [cloud-aws], sites > [2011-09-08 21:14:20,633][INFO][node] [Pyre] > {elasticsearch/0.17.6}[8746]: initialized > [2011-09-08 21:14:20,633][INFO][node] [Pyre] > {elasticsearch/0.17.6}[8746]: starting ... > [2011-09-08 21:14:20,722][INFO][transport] [Pyre] > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > 10.38.111.22:9300]} > [2011-09-08 21:14:26,632][WARN][transport.netty] [Pyre] > Message not fully read (response) for [6] handler > future(org.elasticsearch.discovery.zen.membership.MembershipAction > $1@397b6074), error [false], resetting > [2011-09-08 21:14:26,632][INFO][discovery.ec2] [Pyre] > failed to send join request to master [[Coral][9H4lLBnlQoGTs34jhIPKug] > [inet[/10.84.129.100:9300]]], reason > [org.elasticsearch.transport.RemoteTransportException: Failed to > deserialize response of type > [org.elasticsearch.discovery.zen.membership.MembershipAction > $JoinResponse]; > org.elasticsearch.transport.TransportSerializationException: Failed to > deserialize response of type > [org.elasticsearch.discovery.zen.membership.MembershipAction > $JoinResponse]; java.io.IOException: Expected handle header, got > [110]] > > I verified though the console that I can create keys in the s3 > bucket. Any guesses what operation is failing? > > Thanks! ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![James\_Cook](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@James\_Cook](https://discuss.elastic.co/u/James_Cook)\ **Post date:** [September 9, 2011, 1:39pm UTC](https://discuss.elastic.co/t/ec2-discovery-is-not-working-for-me/5335/3 "2011-09-09T13:39:30Z")
We sometimes use 0.0.0.0 as our network.host value on EC2, so I don't think that is the problem. It looks like the master node in the cluster was discovered, and an attempt was made to communicate with the master. An error occurred while trying to "deserialize response of type". Are you running the same version of ES on both nodes? ---
**Author:** ![Marty1](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@Marty1](https://discuss.elastic.co/u/Marty1)\ **Post date:** [September 9, 2011, 5:24pm UTC](https://discuss.elastic.co/t/ec2-discovery-is-not-working-for-me/5335/4 "2011-09-09T17:24:57Z")
Interesting. I'm running 3 ES unicast (manual IP address) ES boxes running 0.16.2 and I'm trying to bring up a new cluster so it can replace the old one. I think you're right. It's finding an old master. Sounds like I should bump the old boxes up to the same version as the new cluster. I'll give that a try. Thanks! On Sep 9, 6:39 am, James Cook [jc...@tracermedia.com](mailto:jc...@tracermedia.com) wrote: > We sometimes use 0.0.0.0 as our network.host value on EC2, so I don't think > that is the problem. > > It looks like the master node in the cluster was discovered, and an attempt > was made to communicate with the master. An error occurred while trying to > "deserialize response of type". Are you running the same version of ES on > both nodes? ---
**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:54am UTC](https://discuss.elastic.co/t/ec2-discovery-is-not-working-for-me/5335/5 "2017-07-06T03:54:55Z")
Closed on July 6, 2017, 3:54am UTC