[rabbitmq-discuss] RabbitMQ on EC2

Fri Mar 14 20:08:16 GMT 2008

Kyle

Thank-you for this.

We've been experimenting with some of these issues in a public way ...
see Dmitriy's post here: http://www.infoq.com/news/2008/02/ec2

Also (apologies for this but) -- http://es.cohesiveft.com/site/rabbitmq

alexis

On Fri, Mar 14, 2008 at 5:49 AM, Kyle Salasko <ksalasko at gmail.com> wrote:
>
>  Scratch that, I found a solution. An easy workaround is to find the internal
>  (inside the NAT) IP address of any nodes with the domU-... hostnames, and
>  construct the ip-... hostnames from that. For example, Node A from below
>  might resolve to 10.252.56.111, and by manually running 'hostname
>  ip-10-252-56-111.ec2.internal', the problems below resolve themselves.
>
>  The problem seems to arise from the fact that the machines can resolve the
>  first three of the following names, but not the fourth.
>
>  ip-10-251-159-160.ec2.internal
>
> ip-10-251-159-160
>  domU-12-31-38-00-48-A2.compute-1.internal
>
> domU-12-31-38-00-48-A2
>
>  This probably should be automated in AMI creation, but I thought I'd let
>  people know in case they run into the same problems.
>
>  --
>  View this message in context: http://www.nabble.com/RabbitMQ-on-EC2-tp16042914p16044743.html
>
>
> Sent from the RabbitMQ mailing list archive at Nabble.com.
>
>
>  _______________________________________________
>  rabbitmq-discuss mailing list
>  rabbitmq-discuss at lists.rabbitmq.com
>  http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

-- 
Alexis Richardson
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)